Hi Axel,
Thanks for the interesting usage scenario... as you know, currently
you have to choose the language to be used in Ubiquity and only one is
loaded in at a time. Because the underlying parser is universal and
non-deterministic, however, it would be possible (to a certain extent)
to combine each language's properties at different points of the
parser and add a component to the score which requires (or strongly
prefers) that all the rules that were used in a parse be from the same
language. A simple case of this would be with verb names: we could
search for all the English verb names *and* the Japanese verb names
(for example) at the same time... if we recognize an English verb in
the input, then we could strongly prefer the parses which use English
rules for the rest of the parse. All of this, however, would explode
the already large number of intermediary possible parses to keep track
of and score.
I think this touches on the usability/learnability question of
Ubiquity in various langauges, though — there's a big question about
how we present this interface to users and shape their expectation of
what Ubiquity will be able to understand. If we show users an
introductory video in English, for example, would users feel locked
into having to use English? Alternatively, if we do a better job
presenting the user with Ubiquity in their locale, how should we
present the existence of commands which have yet to be translated to
their locale?
Thanks for the thought-provoking question — I'm looking forward to
working with you on these and other Ubiquity l10n questions!
mitcho
--
mitcho (Michael 芳貴 Erlewine)
mit...@mitcho.com
http://mitcho.com/
linguist, coder, teacher