Quoting Thomas Goirand (thomas@goirand.fr): > hu_HU: 213 fuzzy, 801 not translated > it_IT: 205 fuzzy, 637 not translated > nl_NL: 74 fuzzy, 253 not translated > ru_RU: 35 fuzzy, 24 not translated > de_DE: 36 fuzzy, 27 not translated > zh_CN: 230 fuzzy, 427 not translated > pl_PL: 276 fuzzy, 560 not translated > pt_PT: 206 fuzzy, 807 not translated > es_ES: 209 fuzzy, 622 not translated > fi_FI: 39 fuzzy, 1058 not translated > zh_TW: 248 fuzzy, 685 not translated Except for zh_TW, I suggest that all these translations use only ISO-3166 codes, ie that files are named "fr.po", "it.po", etc. Not "fr_FR.po" or "it_IT.po" If you use fr_FR.po it means that your translation will only be available to users of the French/France locale, which would be a shame as users from, say, Belgium speak the same language (OK, with a funny accent and some weird words from time to time but we're still mutually intelligible...). You can send a call for translations by using the "podebconf-report-po" tool...even for non-debconf translations. For this, go into your po/ directory and run something like: podebconf-report-po --call --withtranslators --languageteam \ --deadline="<some day in the future>" --podir=. \ --package=dtc --notdebconf > > Note that MANY of the strings are very small, and that some are only > country names. I have once found a site to help me doing translations For country names, you should use translations from iso-codes. I suggest you pick up the iso-codes package source tree, then go to "iso-3166". You can merge translations from that package into dtc translations with: msgcat --use-first iso-3166/fr.po dtc/fr.po >NEW/fr.po (example for French, assuming that iso-codes translations are in iso-3166 and dtc files are in dtc/....the result being in NEW Then you can resync this with you POT file: msgmerge -U NEW/fr.po dtc/dtc.pot I hope you get the point...:-) PS: OK for not doing an NMU. I'll send you a summary at the end of the call for translations.
Attachment:
signature.asc
Description: Digital signature