3044
Comment: explain the buld process further
|
3604
rework - team is not any longer in founding process
|
Deletions are marked like this. | Additions are marked like this. |
Line 7: | Line 7: |
This Debian team is currently in the founding progress. At this wiki page the success shall be documented. |
This wiki page documents the work flow and the usage of FreeDict dictionary databases in Debian. |
Line 25: | Line 24: |
git clone https://alioth.debian.org/git/pkg-freedict/pkg-freedict.git | git clone https://alioth.debian.org/git/pkg-freedict/freedict.git |
Line 27: | Line 26: |
Unfortunately, there is none yet :-). |
|
Line 37: | Line 34: |
=== Explanation Of Files Under debian/ === |
|
Line 39: | Line 38: |
[[http://www.freedict.org/en/db-as-xml.html]]. | [[http://www.freedict.org/en/db-as-xml.html]]. Those data is used to construct a freedict.orig.tar.gz (the original source) which is then imported. |
Line 46: | Line 46: |
to get the latest version. | |
Line 47: | Line 48: |
To fetch the latest FreeDict source, one executes | In order to fetch the latest FreeDict source, one executes |
Line 53: | Line 54: |
Usage is explained in the first lines of the mentioned file. After this, the | The usage is explained in the first lines of the mentioned file. After this, the |
Line 58: | Line 59: |
language codes. They can be found at | language codes, used to translate the short dictionary names like afr-deu into long names for package descriptions. They can be found at |
Line 61: | Line 63: |
The build process in debian/rules, rule build basically goes through the directories and executes foo-bar.dict.dz. This currently doesn't work for all dictionaries. | There is a last thing which is auto-generated: debian/control.<br /> Modifications for the source package should be done in debian/control.HEAD, everything else is then generated with {{{ debian/fetchdictdata.py -f }}} == The Actual Build Process == There is essentially only a loop going through all directories and executing <tt>make lang-lang.dict.dz</tt>. One special exception is hung-eng and eng-hun, where the database is extracted from a special file before the above explained run. |
Line 78: | Line 93: |
The plan is to adopt them as soon as the “founding process” is over. |
|
Line 82: | Line 95: |
* Look at maintainer scripts to find out whether those are still needed. * find someone with opendict-knowledge and let them tell us how we add dictionaries to the opendict database |
* find someone with opendict-knowledge and let them tell us how we add dictionaries to the opendict database (or validate whether the old way works) |
Line 85: | Line 98: |
* review old patches under debian/patches.old and commit those upstream, if appropriate |
Translation(s): English - Italiano
FreeDict - free (multi/bi)lingual dictionaries
This wiki page documents the work flow and the usage of FreeDict dictionary databases in Debian.
Contents
About FreeDict
The FreeDict project aims at providing free (multi|bi)lingual dictionary (databases) and this team aims at packaging the latest versions to include at both in Ubuntu and Debian Stable/Unstable.
The preferred editable form of the data is in TEI/XML a file format under active maintenance by the Text Encoding Initiative.
Repository
The source can be optained by checking out:
git clone https://alioth.debian.org/git/pkg-freedict/freedict.git
If you have an alioth account, check out:
git clone ssh://<username>@alioth.debian.org/git/pkg-freedict/pkg-freedict.git
Build Process
Explanation Of Files Under debian/
The database of databases with information about the size, author, name and download destination can be found at http://www.freedict.org/en/db-as-xml.html. Those data is used to construct a freedict.orig.tar.gz (the original source) which is then imported.
For performance issues, the freedict-database.xml (with all the dictionary information in it) is cached, one should run
debian/fetchdictdata.py -x
to get the latest version.
In order to fetch the latest FreeDict source, one executes
debian/fetchdictdata.py -f
The usage is explained in the first lines of the mentioned file. After this, the orig.tar.gz-file can be imported with git-import-orig from the git-buildpackage utilities.
From time to time, one should also update the debian/iso.*-file with the language codes, used to translate the short dictionary names like afr-deu into long names for package descriptions. They can be found at http://www-01.sil.org/iso639-3/download.asp.
There is a last thing which is auto-generated: debian/control.<br /> Modifications for the source package should be done in debian/control.HEAD, everything else is then generated with
debian/fetchdictdata.py -f
The Actual Build Process
There is essentially only a loop going through all directories and executing <tt>make lang-lang.dict.dz</tt>.
One special exception is hung-eng and eng-hun, where the database is extracted from a special file before the above explained run.
Contact
Our mailing list can be joined by sending a mail to pkg-freedict-discuss-subscribe@lists.alioth.debian.org or by visiting the subscription page. The posting address is pkg-freedict-discuss@lists.alioth.debian.org. The archive can be found at http://lists.alioth.debian.org/pipermail/pkg-freedict-discuss/.
We have also an IRC channel, just join us on irc.debian.org in the #debian-freedict channel!
Bugs
The Debian packages have been orphaned, see Debian bug 704967
To do / roadmap (?)
- find someone with opendict-knowledge and let them tell us how we add
- dictionaries to the opendict database (or validate whether the old way works)
package descriptions are autogenerated from data, do the very same with translations, see http://www.debian.org/international/l10n/ddtp
- review old patches under debian/patches.old and commit those upstream, if appropriate