[Toolness Labs] #48: Make Japanese language version of the natural language parser
Trac
-------------------------------------+--------------------------------------
Reporter: jonoscript.wordpress.com | Owner: jono
Type: enhancement | Status: new
Priority: major | Component: ubiquity-firefox
Keywords: |
-------------------------------------+--------------------------------------
Just as a sample case of how parsing could work in other languages, see.
Parsing japanese is pretty easy, comparatively, because it's stack-like
and has particles after most nouns to tell you how they relate to the
verb.
But the verb comes at the end, so noun-first suggestions are even more
important!!
Need a sensible way of deciding whether to use japanese-type or english-
type input parsing. (Preferably a way such that I can easily switch
during our presentation.)
--
Ticket URL: <http://labs.toolness.com/trac/ticket/48>
Toolness Labs <http://labs.toolness.com>
Small projects hosted by labs.toolness.com.
Trac
Type: enhancement | Status: new
Priority: major | Component: ubiquity-firefox
---------------------------------------+------------------------------------
Comment(by blur.myopenid.com):
If the language-specific parts of the parser used a plugin-type API, it
would be a lot easier for other people to develop parsers for other
languages structures too.
--
Ticket URL: <http://labs.toolness.com/trac/ticket/48#comment:1>
Trac
Type: enhancement | Status: new
Priority: major | Component: ubiquity-firefox
---------------------------------------+------------------------------------
Comment(by jonoscript.wordpress.com):
Blur: You're exactly right! My thinking is that it would be easier to
figure out what the plugin-API should actually be after we had two
specific language parsers implemented. So I went ahead and made the
japanese parser, but a plugin-type API is exactly the direction we want to
go, I think.
--
Ticket URL: <http://labs.toolness.com/trac/ticket/48#comment:2>
Trac
Reporter: jonoscript.wordpress.com | Owner: jono
Type: enhancement | Status: closed
Priority: major | Component: ubiquity-firefox
Resolution: fixed | Keywords:
---------------------------------------+------------------------------------
Changes (by jonoscript.wordpress.com):
* status: new => closed
* resolution: => fixed
Comment:
Added in r391 - r396. See the files in chrome/content/jp-nlparser. It's
probably all kinds of buggy and broken right now, but if you want to give
it a try you can do so by going to about:config and setting your
extensions.ubiquity.language preference to "jp".
Japanese versions of commands are in chrome/content/jp-
nlparser/japaneseCmdsUtf8.js. So far I've just done two: hon'yaku
(translate) and keisan (calculate). If you speak Japanese, please feel
free to localize some more commands!
--
Ticket URL: <http://labs.toolness.com/trac/ticket/48#comment:3>
Trac
Reporter: jonoscript.wordpress.com | Owner: jono
Type: enhancement | Status: reopened
Priority: major | Component: ubiquity-firefox
Resolution: | Keywords:
---------------------------------------+------------------------------------
Changes (by jonoscript.wordpress.com):
* status: closed => reopened
* resolution: fixed =>
Comment:
OK, there's one more thing that needs to be done here before the japanese
version is usable -- we need to assign a different keystroke besides
"enter" to mean "execute", because in japanese text input the enter key is
used to confirm a certain character interpretation of the phonetic input.
--
Ticket URL: <http://labs.toolness.com/trac/ticket/48#comment:4>
Trac
Reporter: jonoscript.wordpress.com | Owner: jono
Type: enhancement | Status: closed
Priority: major | Component: ubiquity-firefox
Resolution: fixed | Keywords:
---------------------------------------+------------------------------------
Changes (by jonoscript.wordpress.com):
* status: reopened => closed
* resolution: => fixed
Comment:
Fixed in r398. For now, the right-arrow key executes. This is a little
silly, so I'd love to hear if people have better ideas. I also made the
suggestions display in a sensible japanese word order. So it's looking
pretty good now. Give it a try!
--
Ticket URL: <http://labs.toolness.com/trac/ticket/48#comment:5>