I've updated the bug report
https://github.com/mvysny/aedict/issues/504
with the words you sent me - good find, thank you!
However, the thing is that Aedict currently limits the results to top
200 results (for performance results). So it would be tricky to bend the
search to show all JLPT words. However, that may not be necessary now
since you have the CSV files?
Anyway, let me fix the JLPT tagging algorithm by using your CSV files as
the source of data.
Thank you,
Best regards,
Martin
On 11.12.2018 2.23, Joey Payne wrote:
> Hi, sorry for the late reply, I've been busy lately.
>
> The source is
skritter.com <
http://skritter.com>. Not sure if you're
>> <mailto:
aedict-users%2Bunsu...@googlegroups.com>
>> > <mailto:
aedict-users...@googlegroups.com
>> <mailto:
aedict-users%2Bunsu...@googlegroups.com>>.
>> > For more options, visit
https://groups.google.com/d/optout.
>>
>> --
>> Please support the Aedict development, by subscribing for
>> Aedict Ultimate in Google Play - thank you very much!
>> ---
>> You received this message because you are subscribed to the
>> Google Groups "aedict-users" group.
>> To unsubscribe from this group and stop receiving emails from
>> it, send an email to
aedict-users...@googlegroups.com
>> <mailto:
aedict-users%2Bunsu...@googlegroups.com>.