Quote:
Originally Posted by Ceiyne
When I looked that up, I found that the project had been retired and Pyglossary was the tool recommended by the Penelope developer. From what I understand, the Penelope code was incorporated into Pyglossary.
|
Yes, that's correct. Recently, the plugin was rewritten to match dictutil's code.
Quote:
Originally Posted by Ceiyne
I got responses from both the Pyglossary developer and the dictutil developer on one of the issues I opened and it sounds like Japanese is not fully supported by Pyglossary/dictutil.
|
Yes, the dictutil developer is me, and I've responded to both issues.
Quote:
Originally Posted by Semwize
Wonder how it is with the Japanese language.
Although geek1011 writes that ALL existing tools will not handle correctly. I don't know if he also included Penelope on the list.
|
That's also correct. None of the existing tools handle the Japanese prefix generation and word matching algorithms, and nobody's bothered to reverse engineer it yet.
Quote:
Originally Posted by Semwize
As I understand it, the latest versions of Pyglossary are using dictutil and not Penelope. That is why I suggested that you see if the same error will occur with Penelope. It turned out that yes, unfortunately.
|
Yep.
Quote:
|
It is strange that for so many years of the existence of the Penelope project, they did not pay attention to this. Or I just didn't see.
|
Penelope was created during the time of v1 (pre-2017) dictionaries. At that point, the prefix generation was much simpler. In addition, it didn't try to handle variants , images, or other advanced features at all; it stuck to simple word-definition pairs.
Dictutil handles v2 dictionaries, and I'll be releasing v3 (post-fall-2020) dictionary support as soon as I have enough time. Note that I should be able to work around the Japanese differences entirely using the new v3 prefix exception mechanism.