Greetings.
Yes, it seemed to work fine on both WordNet 3.0 and 3.1 when I called
WNConverter directly. (I didn't do rigorous testing on the output,
though no exceptions or error messages were produced.)
The error message reported by Issue #120 is caused by using an incorrect
extJWNL file. (The format changed in extJWNL 1.8.) This is not a
problem with Uby but rather in your choice of the properties file that
you passed to the WNConverter() constructor.
However, I see that in Commit 391d80c, Mohamed created a new module that
calls WNConverter() with a hard-coded extJWNL properties file, and this
file is also for the wrong version of extJWNL. I don't think it's a
great idea to hard-code an entire properties file in the first place,
but I will nonetheless commit a quick fix for the problem.
Regards,
Tristan
--
Tristan Miller, Research Scientist
Ubiquitous Knowledge Processing Lab (UKP-TUDA)
Department of Computer Science, Technische Universität Darmstadt
Tel:
+49 6151 162 5296 | Web:
https://www.ukp.tu-darmstadt.de/