(maybe keep -i18n and -l10n-english CC'ed) 23:46 < Kamion> bubulle: would it be possible for me to create an en_GB.po that deliberately left most strings untranslated, but just translated strings where American and British spelling differ?
Well, at this moment, incomplete PO files will be treated by po-debconf stuff as "not to be used". Indeed, for a given debconf template, all strings have to be translated and not fuzzy for being incorporated in the final templates file after po-debconf does its magic grabbing together the translation in the files. If one string is either untranslated (aka empty) or marked "fuzzy", then the original templates are used. So, if you want an en_GB file that works for templates where you need changes for British spelling, you must have complete "translation" at least be copying the stuff from the colonies in the msgstr....:-) One easy way to do it is just copying all msgids to msgstr and then make corrections for British spelling. This will lead to a full British "translation"...the price to pay is cluttering up the packages with a bit more stuff, indeed one more language.....which may be a problem for packages which lead to size constraints (the initrd stuff, mostly). The extra stuff will be useless most of the time, except in few occasions. The hard way is a partial en_GB.po filebut you must then take care to "translate" complete templates to have it working. What I fear here is creating what we call in French a "précédent" (I don't have the English tsl...hope you get the point) and then have nl_NL "translations" when Dutch people do not agree with the belgian influence in the Dutch team.....or es_AR translations for Latin American way to talk (I talked about that with Margarita...the Spanish team seems to have agreed on a common ground, though), and so on.... -- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]