This step is different from other ones, because its design has an influence on the whole system. And in fact we should first focus on the features we want to have at this stage.
Translated strings are part of Debian packages, and are thus in the hands of package maintainers. On the other hand, translators tend to cooperate in order to prevent duplicated efforts, and in practice it is common to have translation teams with one or several leaders who drive their language teams. Language coordinators have an eye on all packages to make sure that their translations are included by package maintainers, and that everything runs fine with their language. Of course they need help from dedicated tools. At the moment there are status web pages for d-i[1] and another one more general for all Debian packages[2]. Some translation teams have their own status pages[3] with more details. Let us review previous mails: * Step 1: Import of translatable strings At this stage, developers sent new original strings and maybe their current PO files. Language coordinators want to know if original strings have changed, and also if PO files have been altered by the package maintainer. In this case, they want to review these changes to either synchronize PO files stored in the l10n system, or file a bug report against this package if these changes have to be reverted. * Step 2: Translation Pages like [3] provide all the needed informations. * Step 3: Export of translations Translations are available, and language coordinators need to check if they are included. If not, they may ping the maintainer, and perform an NMU if there is no reply from the maintainer. [1] http://people.debian.org/~seppy/d-i/translation-status.html [2] http://www.debian.org/intl/l10n/ [3] http://dutch.debian.net/ Denis -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
