I have a problem with Aedict which started from a recent update. If I have
my search filter settings to match the start of a word, it will not match
exact matches as well. For example, when I search for 近所, the actual entry
for that word will not show up unless I change the settings to exact match.
Would it be possible to go back to the original way of matching so that
exact matches also come up when searching with starts with?
Original issue reported on code.google.com by martin.v...@gmail.com on 24 Dec 2014 at 7:22
The text was updated successfully, but these errors were encountered:
Works for me (please see attached screenshots). Please attach your screenshots,
to demonstrate the issue on your phone. You can create screenshots easily, by
long-pressing the power button and the volume down button.
Original comment by martin.v...@gmail.com on 25 Dec 2014 at 9:16
Sorry about this. When taking the screenshots, I saw that the search type was
set to Verbs. I've never intentionally used that filter before, so my eyes
always skipped right over it.
However, take a look at the attached screenshots as there seems to be a
When Verbs is selected, 近所 will appear when "match exact" but not when
近所 isn't a verb, so it shouldn't appear either way.
Original comment by jacobhic...@gmail.com on 25 Dec 2014 at 9:33
Yes, I noticed this behavior too. Obviously, 近所 is not a verb per se, so
Aedict should display 0 results. However, when 0 results are found, a fallback
sentence analysis kicks in, which will try to split the "近所" sentence into
separate words, and it succeeds - it finds exactly one word, 近所.
This needs three fixes:
1. an information that only verbs are being searched for;
2. if the analysis fallback returns only one word, discard it;
3. otherwise, add an information that analysis fallback has been performed.
Original comment by martin.v...@gmail.com on 25 Dec 2014 at 11:49