Background: we have a verb in Japanese called "Flickrで検索する",
which is "search with flickr"
1. Input: "flick", we get the flickr verb as an option (it's kind of
low, but okay)
2. Input: "flickr", we get the flickr verb as an option (kind of low,
same as (1))
3. Input: "花火をflick", we get the flickr verb. OK. (searching
flickr for fireworks)
4. Input: "花火をflickr", we *DO NOT* get the flickr verb. AT ALL.
(I recommend you try all of these in the playpen so you can see lots
of suggestions... the scoring is not the issue... some parses aren't
being generated at all.)
If you use the playpen and turn on the "display parse info", you'll
see that in input 4, "Flickrで検索する" is not showing up as a
verb match at all.
It looks like in input (4), the final "r" is being picked up as the
first letter of "run selector-selector" and it thus isn't finding the
longer "flickr" match. This is a huge bug. We should be getting *both*
of those verb matches... the "flickr" match should simply get a higher
verb score.
mitcho
--
mitcho (Michael 芳貴 Erlewine)
mit...@mitcho.com
http://mitcho.com/
linguist, coder, teacher
I don't get parses at all in playpen with these inputs. The parsing
seems to stop before step 9 somehow.
Anyhow, this seems like an inherent problem of trying to do the final
match with a single regexp.
demoParserInterface.currentParser._patternCache.verbFinalTest("花火をflickr")
// => ["花火をflickr", "花火をflick", "r"]
I think we want suffixes for verb-final matching. Not prefixes.
Update for this behavior. I get this error when it stops:
Error: [Exception... "'JavaScript component does not have a method
named: "onTextEntered"' when calling method:
[nsIAutoCompleteInput::onTextEntered]" nsresult: "0x80570030
(NS_ERROR_XPC_JSOBJECT_HAS_NO_FUNCTION_NAMED)" location: "<unknown>"
data: no]
Looks like this is related to Utils.history and nouns using it
(noun_type_url/noun_type_awesomebar).