From: Jutta W. <jw...@wi...> - 2005-07-12 00:26:52
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Am 10.07.2005 um 06:34 schrieb Michael Bunk: > I cannot know why you ask when you don't write it. Okay, it is not standard, tha people read manpages at all. > Yes, there is nothing more precise than that manpage - no > spec. You can only read the source. I'll have to finde someone knowing more C than I do. >> And wrong sorting makes the dict files work with Serpento? > For the last question, yes, because serpento sorts each index > before using it. > That is why it has something that it calls "cache". How did you > generate your > own dicts? I create them with a perl script. The alphabetical order is build using the Collate module. The oder is not by byte. But if I reduce an index file to only a few entries, which are ASCII only, and everything is ordered then by byte values, the dicts still do not work with dictd. > Where to find more about perl collocate? Did you make you index > with it? Collate, sorry. Perldoc Unicode::Collate. >> - Is there a way linking between different dicts? >> > > No standard. Hmm... Would a good idea to have one as already clients are using such features - undocumented. > Overthere is serpento and I cannot see anything wrong with the dictd > configuration. la-sorciere has Serpento installed, yes, Dictd did not work with the utf8 file (neither mine nor those fromn freedict (fetched from the web). I'd install a dictd there too, if it was possible. But the packages conflict. You may get one of those files installed on la-sorciere at http:// www.witch.westfalen.de/debian-women/dict/ Taking dward.en is a good idea as there ar no special UTF-8 characters in it. hmm.. seems I munged my answers. ;-) If I find someone who gets the needed information out of the dictd source code, I'll try to dcucument it a bit. greetings Jutta - -- http://www.witch.westfalen.de http://witch.muensterland.org -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (Darwin) iEYEARECAAYFAkLS8iwACgkQOgZ5N97kHkcSvwCgpzIlECu6B6QL8ubnlc4uPQS+ KTMAn1pId/6QeQFCOZ1iSKM8ZqNdapMH =wfI2 -----END PGP SIGNATURE----- |