Hello,
It would be nice to start working on the translation of the (next) Release
Notes.
Of course the Release Notes for the next release are not yet available,
but there are some tasks that can be started in advance:
[1] docbook-xsl has no l10n support for the following languages:
be, ml, nb
The process for providing a new language is described on:
https://docbook.svn.sourceforge.net/svnroot/docbook/trunk/gentext/locale/README
I will contact the translators for the languages which are not yet
supported.
Other teams can also review the current docbook translations on
https://docbook.svn.sourceforge.net/svnroot/docbook/trunk/gentext/locale/
[2] Updating translations
Here are the current statistics:
be: 827 translated messages, 20 untranslated messages.
de: 846 translated messages, 1 untranslated message.
es: 789 translated messages, 46 fuzzy translations, 4 untranslated
messages.
fr: 846 translated messages, 1 untranslated message.
it: 847 translated messages.
ja: 846 translated messages, 1 untranslated message.
lt: 707 translated messages, 46 fuzzy translations, 94 untranslated
messages.
ml: 795 translated messages, 47 fuzzy translations, 5 untranslated
messages.
nb: 796 translated messages, 46 fuzzy translations, 5 untranslated
messages.
pt: 846 translated messages, 1 untranslated message.
ro: 847 translated messages.
ru: 796 translated messages, 46 fuzzy translations, 5 untranslated
messages.
sk: 796 translated messages, 46 fuzzy translations, 5 untranslated
messages.
sv: 847 translated messages.
vi: 796 translated messages, 46 fuzzy translations, 5 untranslated
messages.
zh_CN: 795 translated messages, 47 fuzzy translations, 5 untranslated
messages.
zh_TW: 636 translated messages, 161 fuzzy translations, 50 untranslated
messages.
ca: ~100% (~100.00%).
cs: ~100% (~100.00%).
pt_BR: ~58% (~57.64%).
[3] Updating the Release Notes build system.
This includes:
+ Checking if it is still needed to use xmlroff instead of dblatex for:
be ja ml pl vi zh_CN zh_TW
+ removing workaround for old version of some tools
+ updating PO files for the new version of the build system
[4] fixing the build warnings (or raise bugs for the build tools)
[5] branch the Lenny current release notes
There is still some work to be done on the Lenny Release Notes, so
this should still wait until the release-notes and upgrade-reports
bugs get some fixes.
[1] and [4] can be done right now.
Updating the Release Notes build system ([3]) should not disturb the Lenny
Release Notes, so it might be better to wait for [5].
Updating the translation [2] of the Lenny Release Notes is also possible
now, without waiting for the other tasks.
After [5], translation teams should decide if they want to continue
updating the Lenny Release Notes translation.
[5] should wait to avoid having to merge too much between the trunk and
the Lenny branch.
Best Regards,
--
Nekral
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
