Re: Directory for dictionary databases
Andreas Tille <tille@physik.uni-halle.de> writes:
> But in my opinion it is a bad solution if every "translation related"
> data should be stored in different directories. I think a directory
> structure should be as logical as possible. Im not familiar with
> FHS and havn't enough time to learn about it. But in my opinion it
> is necessary to store data together if they have the same purpose.
> I would suppose to store translation related data in
>
> /usr/share/lang
> or
> /usr/share/trans [-lation]
> or
> /usr/share/lingua
> or may be
> /usr/share/lingua-mono AND
> /usr/share/lingua-bi (lingua-multi)
>
> The latter case means to store monolingual databases like wordnet and
> dict in lingua-mono and bilingual databases (I plan to maintain a
> English-German dictionary) in lingua-bi. (We should think about
> the Euro-wordnet project which is multilingual.)
> Supporting this hierarchie wie can store in this directory single
> file dictionaries and in a subdirectory if there are more files like
> in the case of wordnet.
I don't think a mono-lingual dictionary is "translation related"
data. I agree that bi-lingual files deserve a separate location, but
a structure such as you suggest would only be useful if accepted as a
standard. So far, at least, the FHS committee has avoided specifying in
much detail the subdirectory structure (/usr/share/man and
usr/share/dict are exceptions). They do recommend :
| Any program or package which contains or requires data that doesn't need
| to be modified should store that data in /usr/share (or
| /usr/local/share, if installed locally). It is recommended that a
| subdirectory be used in /usr/share for this purpose.
We should keep in mind that databases for programs like dictd (I
don't know if this is true of WordNet) are formatted so that it is
difficult, at best, to access them with other programs, so there is
less need to keep them together.
> I think if we don't do that we will end up in so many directories in
> /usr/share after some years that it would be horror. Think of NLS
> and such stuff. There will be more and more needs for dictionaries
> and we should do it right from the beginning.
I don't see this as too much of a problem. Look at /usr/doc, with
a subdirectory for every executable.
> Please foreward this to the FHS team because I'm not able to involve
> in this theme.
I have no contact with the FHS committee, and I don't have time
to get involved in it either. There is an FHS mailing list, but I
don't know its address. The current draft of the FHS is available at
tsx-11.mit.edu:/pub/linux/docs/linux-standards/fsstnd.
Bob
--
_
|_) _ |_ Robert D. Hilliard <hilliard@flinet.com>
|_) (_) |_) Palm City, FL USA PGP Key ID: A8E40EB9
--
To UNSUBSCRIBE, email to debian-devel-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: