Hi! Am 12.08.2006 um 00:56 schrieb Quentin Mathé:
Now I wonder how I'm going to get the dictionaries when the application is launched. The resource-solution is okay for the Jargon file, but other dictionaries may have other licenses. I certainly don't want to get involved with licensing issues. ;-)What are the usual licenses of other dictionaries. Do you know a page where such dictionary license are listed and avaible for reading?
Most seem to be free, but you can never be sure if you won't find one which isn't.
http://www.dict.org/links.html has a list of dictionaries (scroll down!). The Jargon file seems to be okay for use (http://catb.org/ jargon/html/online-preface.html , look at the top), WordNet seems to be provided "AS IS" (see http://wordnet.princeton.edu/license) and FOLDOC is GNU-FDL (see http://foldoc.org/?Free+On-line+Dictionary).
I couldn't find out Webster's license. But maybe I just didn't look close enough. It's probably free.
Another interesting thing I stumbled upon on Wikipedia is Wik2Dict: http://www.industree.org/guaka/wiki/Wik2dict It converts the Wikipedia to the dict format. I didn't try it yet, but the resulting files are probably too big to be distributed with Etoile. ;-)
The constraints I keep in mind are:A) I probably want to have icons for the dictionaries later. Bundles would be perfect for that, but if this is not acceptable, the icons can also be stored in the main application. (There don't seem to be more than 20 appropriate dictionaries in the public domain.)Are most of dictionaries provided with a dedicated icon? How is the icon provided/packaged usually? Is there a usual location?
No. They usually don't have an icon. In fact, I didn't see a single one. I imagined it to be fun to have a quick visual hint that tells you which dictionaries are active. (At the moment, I don't know an appropriate location for it, though. It's just an idea for future improvement. I don't want to break the possibility to implement this in this early stage. :-))
The way I'd package the icons would be to save the xxx.png file along with the xxx.index and xxx.dict.dz (where xxx is the short "base name" of the dictionary, e.g. "jargon").
4) Fetching and installing dictionaries as part of the build process.- Licensing issues just *moved* to the time when Etoile is shipped in binary form. :-/+ Easy to use + "Bundles" (see above) can be usedThat's going to make Étoilé a lot more heavy, taking in account they are a huge number of dictionaries available, no? I don't think providing all of them out of the box is a good idea. It's better to give the user the opportunity to install the dictionaries they want. Though providing a default set of five or ten dictionary is surely a good deal.I'm in favor of a basic set of dictionaries with the possibility to extend it by relying on solution 2) and 3) … solution 3) would be the last fallback, always working.Here is my take on this issue :-)
Okay. Thank you for the long answer! :-)Now that I discovered the Gzip support in the GS NSFileHandle source code, it should be no problem to use it. On OSX, I'm still not sure what to do, but that will turn out then.
Here's what I am going to do now:
A. Dictionaries will be searched for in the following locations:
1) System wide dictionary paths for several OS's.
2) System wide Etoile dictionary path
3) $HOME/GNUstep/Library/DictionaryReader/Dictionaries/
B. DictReader ships with a list of known dictionaries (with URLs),
that can be downloaded directly from the application and that will
extract directly to the user's local dictionary path in $HOME/GNUstep/
Library/DictionaryReader/Dictionaries/. It'll probably need FTP
support then.
Attached to this mail, you'll find a simple GUI sketch of the preferences window.
-Günther
<<attachment: dictreader-pref-sketch.jpg>>
_______________________________________________ Etoile-dev mailing list [email protected] https://mail.gna.org/listinfo/etoile-dev
