Hi Osma! Pleased to see that you progressed on this task :). Our project really needs someone to take on this job.
> I've been trying to build an updated doudoulinux-l10n-fi package using the > latest translations from Transifex and the scripts found in the DDL SVN > repository, so that I could try out my translations for real (instant > gratification, if you remember my previous posting about translator > motivation). Note that for real instant gratification, a quick, first step could be to include in DDL 2.2 or 2.5 a script that just compiles Transifex PO files into MO files in /usr/share/locales/. We would not care right now about TS files and specific tricks, but this would still allow many applications to be up to date with Transifex at any time, without making a Debian package. > # apt-get install subversion unaccent debhelper fakeroot python-polib > python-pip > # pip install transifex-client Hem, I don't remember if I've written something somewhere about l10n prerequisites… Obviously tools required to compile PO/TS files are missing in this list. They should be in packages gettext and libqt4-dev. You may also need the package translate-toolkit to get the command po2ts, as well as intltool if you want to deal with application icon files. > 1. Checkout DDL l10n code from SVN: > > $ export LANG=en_US.utf8 > (just to get all errors in English so I can post them here!) > $ mkdir doudoulinux-svn > $ cd doudoulinux-svn > $ for dir in lang live packages; do mkdir $dir; svn co > http://svn.gna.org/svn/doudoulinux/$dir/trunk $dir/trunk; done > (this took a while and requires around 1GB disk space) I'm surprised to see that trunk/ in these three directories uses up to 1GB. You probably don't need live/ though. > 2. Set up transifex connection > > $ cd lang/trunk > $ ./transifex init all > (this prompts for transifex username and password and stores them in > ~/.transifexrc) Ok, important to know this step obviously! > I had some trouble with this at first, because the Transifex URL used by > transifex-client has changed from http://www.transifex.net to > https://www.transifex.com and the client complains about the changed URL. > I had to change the URL in the transifex script and also in all .tx/config > files. Patch available here: http://iki.fi/osma/transifex.net-com.patch Great, I must say I haven't fetched anything from Transifex since version 2.1, in early December. You'll probably need a DDL SVN write access to be able to push your changes by yourself in the future. See: https://gna.org/projects/doudoulinux/ You can create a personal branch in lang/experimental/ or packages/experimental/ if you want to work without risking to break something in the trunk. > 3. Pull the latest translations from Transifex > > $ ./transifex pull all fi > > This seemed to get the latest Finnish translation updates - actually only > one change I deliberately did to gcalctool translations, the others seemed > to be already up to date in SVN. This takes a while to run. Yes, it can last up to one or two hours if you try to get all the languages for all the ressources. > 4. Prepare the localization source package > > $ cd ../../packages/trunk/l10n > $ nano make-l10n.sh > (edited the AUTHOR declaration near the beginning, in order not to > impersonate Jean-Michel!) Jean-Michel doesn't sound Finnish enough? ;) Note that currently debian/changelog is not versionned, which is probably an issue since someone rebuilding the package on his computer may use version numbers that have already be used… > mv: cannot stat `../../../lang/trunk/apps/work/goldendict/ts/fi.qm': No such > file or directory > mv: cannot stat > `../../../lang/trunk/apps/education/tanglet/ts/tanglet_fi.qm': No such file > or directory > mv: cannot stat > `../../../lang/trunk/apps/multimedia/pianobooster/ts/pianobooster_fi.qm': No > such file or directory > mv: cannot stat > `../../../lang/trunk/apps/multimedia/stopmotion/ts/stopmotion_fi.qm': No such > file or directory > mv: cannot stat > `../../../lang/trunk/apps/multimedia/hydrogen/ts/hydrogen.fi.qm': No such > file or directory > mv: cannot stat `../../../lang/trunk/apps/multimedia/vmpk/ts/vmpk_fi.qm': No > such file or directory I'm pretty sure the command lrelease that compiles TS files is missing. Install libqt4-dev and retry! > copying extra l10n files > ERROR: no script '../../../lang/trunk/apps/work/laby/.locale.sh' for > '../../../lang/trunk/apps/work/laby/.locale' > ERROR: no script '../../../lang/trunk/apps/work/laby/levels.orig.sh' for > '../../../lang/trunk/apps/work/laby/levels.orig' > WARNING: no data directory > '../../../lang/trunk/apps/education/gcompris/voices/fi', aborting… > copying '../../../lang/trunk/apps/education/khangman/data/fi' into > 'doudoulinux-l10n/data/usr/share/kde4/apps/kvtml' > […] > Anyway I continued, assuming that the errors are simply due to missing > translations and not any show-stoppers. > Non blocking errors in my opinion too. > cp: cannot stat `debian/tmp//usr/share/apps/goldendict/locale/fi.qm': > No such file or directory dh_install: cp -a > debian/tmp//usr/share/apps/goldendict/locale/fi.qm > debian/doudoulinux-l10n-fi-updates///usr/share/apps/goldendict/locale/ > returned exit code 1 I think this error is really due to the missing command lrelease. The package should get compiled after installing it, at least I hope so. > I could go on investigating why the script fails, but since I've already > tried a number of things I thought this would be a good time to ask for > help. I'm not sure which of the above warnings and errors are serious and > which are expected. So what am I doing wrong above? Are the scripts > supposed to work on DDL 2.1 (squeeze), or should I try a wheezy-based > system instead? No, I've never tested them on Wheezy and I'll probably won't do before we migrate translations to Wheezy, for DDL 3.0. > If I can get this working this could be easily turned into a HOWTO for the > website. This way translators could actually see the results of their hard > work without having to prod Jean-Michel or wait for the next release :) I agree, this information should be made available in our developer's section on our website. I'll create you an account as soon as possible so that you can write a new page about how to get fresh translations into DoudouLinux. This is an important piece of information for our contributors (around 150 people!). Thanks for your work! -- Cheers, JM.
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Doudoulinux-lang mailing list [email protected] https://mail.gna.org/listinfo/doudoulinux-lang
