Consolidating replies to two mails:
Andreas Tille wrote:
> I have no idea how strict we should be about the length of lines
> in the output. I just adopted this check from the previous maintainer.
> Moreover the problem is just in the starting comment:
>
> $ grep "^.\{73,\}" wn.dict
> the follow
Hi Sebastian,
I just implemented the "allow two long lines sloppyness test" and
putted the result into my private package repository that now is
able to build the dict-wn package again. I installed it and you
are right that
dict -d wn test
works now perfectly, but ...
$ wordnet toast
On Tue, 5 Jun 2007, Sebastian Hagen wrote:
You're only feeding it index files here, which results in it treating some
of those as data files, and failing horribly to parse them as such. As the
output says:
Opening index file 'data/index.adj'...
Opening data file 'data/index.adv'...
Ahh, this e
Andreas Tille wrote:
> Unfortunately there is a problem:
>
> ...
> mkdir -p data
> for file in ../../dict/dbfiles/data.* ../../dict/dbfiles/index.[anv]* ;
> do ln -s ../$file data ; done
> LC_ALL=C python wordnet_structures.py `ls data/index.[anv]* | sort`
> Opening index file 'data/index.adj'...
On Tue, 5 Jun 2007, Sebastian Hagen wrote:
Since wordnet is (even in its outdated version) one of the most useful
general-purpose dictionaries for dictd, this is highly unfortunate.
Definitely.
Digging through the hundreds of lines of string-processing C code of wnfilter
to find out what exa
Package: wordnet
Version: 1:2.1-5
Severity: wishlist
The dict-wn package hasn't been available for quite a while now. the
reasons for this are explained in the discussion to bug #403030: the
program that has been used to convert the wordnet database into dictd
format, namely 'wnfilter', doesn'
6 matches
Mail list logo
