tevino
commented
9 years ago I found similar issue in Chinese, the pinyin of the word included with the word itself, just like the romaji is included in Japanese too.
I guess there should be a more general solution for this, instead of parseNihongoWord :smiley:
For example, if I'm trying to save the entry 「汗」 with BetterDictionary, i got 「汗【あせ】」. So when I click the saved entry, I actually load 「汗【あせ】」 into the search box, which definitely results in 「No entries found.」. Therefore I added a method to the load process to correctly save the Japanese word entry as 「汗」.