Maintaining dictionaries available with the latest version of DictionaryForMIDs

Here is what needs to be done for the dictionaries that can be downloaded from our web site (apart from the DTS dictionaries for which Zdenek already did write the scripts):

1. Collection of the dictionaryinputfiles
As of now, for the dictionaries that can be downloaded from our web size, we do not have a centralized archive of the dictionaryinputfiles ! For example Gert has the dictionaryinputfiles for some dictionaries, Jeff has several more, and others have a few.
So we need to collect all the dictionaryinputfiles, along with all related files, such as copyright statements or possibly source files. Plus for each dictionary the file DictionaryForMIDs.properties needs to be stored. All of those file should be put into an archive.

2. Generating the dictionaries with DictionaryGeneration
Each of the dictionaryinputfiles needs to be run through DictionaryGeneration. This should be automated by a script.

For bi-lingual dictionaries (many are bi-lingual), this a little more complicated. See under the description of the property languageXHasSeparateDictionaryFile the "For documentation, see here".

3. Creating the files DictionaryForMIDs.jar/jad with JarCreator
The generated dictionaries need to be put in a Jar-file with the latest version of DictionaryForMIDs. This is done with JarCreator. Again this should be automated by a script.

4. Putting the files DictionaryForMIDs.jar/jad in a ZIP package
By a script, the files DictionaryForMIDs.jar/jad need to be put in a ZIP package, together with README & COPYING file, plus if appropriate additional copyright statements or other files. The Java Jar tool can be used for this, or 7-zip, or whatever else ZIP-tool is preferred.

5. Publishing the ZIP packages on the web site
Finally, the ZIP packages need to be published for download on the DfM web site. Getting the files there involves uploading them to the SourceForge File Release System.
This step 5 probably requires some co-ordination with Peter (Peter is responsible for publishing dictionaries).


In general, I'd propose that all data (the archive of inputdictionaryfiles, the scripts, etc.) are stored on SourceForge once established. So this will be a long-term contribution to the DfM project.

Actually, I believe that the main focus of this task is not only writing scripts, probably the scripts can be done rather quickly; but beyond scripts there are other things that need to be done: co-ordinating with other people, getting clarifications and so on.

As always, contact us for questions !