A lot of these are edge cases, but not ones specific to the one word, so the fixes are improving larger sets of words leading to better matching overall. Thanks!
Two more things. First, I did a sentence with an exclamation point in it, and the parser lists it as an undefined word in the word list. Second, I did a sentence with 写真を撮ろうとした, but the parser only binds とした to the verb 賭する; the entry for とする meaning "to try to" is not an option.
Not a parser problem but related to sentence binding. (Thought we had a thread for that?) I wanted to bind the term 黄金（こがね）. But as it was written in hiragana my only options were 小金 and 金 although all three versions exist in the dictionary.
For a sentence with 猛暑がないといいんです。, the part ないと gets automatically parsed as ナイト and has to be rewritten in hiragana within the parser pop-up to parse correctly; trying to use parentheses just makes it list the components as undefined.
I was going to fix a sentence one sentence that has "へいく途中" because いく is indicated as "something that continues into the future". But there are 36 sentences with these words, with the same mistake And then there are 382 occurences of "へいく". The majority has the same mistake. In those sentences, へ is correctly attributed to "indicates direction...". So a new rule could be useful...
Wow, there were a lot of those. Did a mass sweep, should be better. Without being able to look at all of them, I let them stay the same *if* the いく were preceded by a て verb, as that is the only way it can be used with that meaning.
Another issue similar to my last one, but in the opposite direction. A sentence with ハイクに行く gets displayed as はいくに行く in the parser popup. Thankfully, in this case ハイク still appears as an option in the dropdown, but regardless, the parser is still having the problem where it rewrites sentences with different kana, and doesn't suggest the most likely definition based on the script used (since it was in katakana, the default definition recommendation should have been for ハイク, not 俳句).
