Do you still need me to send you a diff?

The issue is that we then need to explode the number of possible argStrings before sending it to argFinder, as we don't want to only get parses where "a-las" is used as a delimiter. We may also want the parse which takes "a" as a delimiter and actually sends "las" to the argument, for example, so we'd have to give both "agr meeting al calend a las 2pm" and "agr meeting al calend a-las 2pm" to argFinder. If there are ever multiple multi-word delimiters in an input, this juggling would add an additional layer of recursion to the parser which I'd rather avoid.

I was also thinking that maybe the role could be "a-la" and the parser could capture "a la" and identify it as that role. I think the current Ubiquity does something like that? That way one could type: "agr meeting al calend a las 2pm"

And the parser would read it as: "agregar meeting al calendario a-las 2pm"

Would that be possible?

Anyway, I guess grammatically (linguistically?) the words la, los, las, etc. aren't really part of the role, so the cleanArgument may be a more solution.

Thanks!

That said, perhaps there are cases with other languages where multi-word delimiters are seriously required… the main test would be a case where one delimiter is the substring/subword of another delimiter, and they are for different roles, so that they're in competition. As long as we don't have that, though, I think we're safe for the time being.

I added a new method to Parser called cleanArgument which is called whenever an argument is assigned to a role… you can override this method in the Spanish parser so that it strips "la" and "las" off the beginning of arguments. Give that a try.

Re: move… I noticed that yesterday as well while making my demo video. I'm going to try to figure that out today.

Re: "a la"… yes, this is definitely something we need to allow. My immediate response would be that maybe we can join these instances into "ala" or "a-la" in the wordBreaker method and then deal with them as single words later, but then that doesn't allow having both the parse where that goal is used and the parse where that goal is not parsed… I think the best thing to do is to build multi-word delimiter support into the argFinder method. I'll work on that today as well.

Thanks for bringing these issues up!

I have a few comments, though. The "move" command seems to have issues. The portugese example doesn't get picked up, and neither does the Spanish version I'm working on, and curiously, both Portuguese and Spanish use "ir". I wonder, is "ir" too short? And the longer portugese version "vai" does not get picked up either.

Also, for the "goal" and "time" roles, I can't seem to be able to use multiple words. A very common goal role could be "a la". And the time role is always either "a las" or "a la", never a single word. Being restricted to a single word for the roles doesn't feel natural at all in Spanish.

Thanks!!!