Big Issues and Small Issues with Parser 2
Jono and I had a good conversation this morning on IRC about the remaining Big Issues which are blocking the release of Parser 2 as the default parser for Ubiquity. Here are our Top 4 Big Issues:
- Some commands’
preview
’s andexecute
’s are not working properly (trac #652). This could be an underlying issue with some pipes not rerouted correctly in Parser 2, or it could be that the commands have not been rewritten correctly to take advantage of Parser 2. - Flesh out how to localize resources, like commands and nountypes. We started a conversation on this subject a few weeks ago but we never reached a resolution. This blocks issues 3 and 4 below.
- We need to standardize a format for commands for Parser 2. As noted in last week’s meeting (among other places) Parser 2 will require at least some modification to all commands. Jono and I came up with a simple hybrid format for commands which specify
takes
andmodifiers
for Parser 1 andarguments
for Parser 2, but until we figure out how exactly the localization of commands will work, we can’t write a definitive standard. - Enable nountype localization. While the most popular nountypes used are those that ship with Ubiquity, it is important to come up with a localization process which can apply to custom nountypes as well. Nountype localizations need the ability to either (1) replace the
_name
only, or (2) replace both the_name
and thesuggest()
logic, as both cases will be necessary.
Given that Big Issue 3 and Big Issue 4 are both dependent on Big Issue 2, there clearly needs to be a continued public discussion of how we should make these resources localizable. I look forward to this discussion taking place at tomorrow’s joint (general + i18n) Ubiquity meeting.
In other news, here are some Small Issues:
- Add a switch for parser version and language settings: Jono’s already made a space for this in the new “Settings and Skins” page in
about:ubiquity
. He’s on it. Like a bonnet. - Magic word (anaphor) substitution is not yet working properly. This needs to work both when there is an explicit magic word and when there are simply missing arguments.
- The position of suggested verbs is always sentence-initial (trac #655). This also requires that we can specify whether verb name localizations are sentence-initial forms or sentence-final forms.1
- …
Let’s hit the code!
-
German, Dutch, and Greek, for example, are all languages where there are both command verb forms which are sentence-initial and sentence-final. ↩