El mié, 18-06-2008 a las 02:13 +0200, Marc Fargas escribió: [snip] After this thread and talking on IRC with Ramiro it seams that a good practice would be, given those two types of untranslatables:
* The ones left blank on purpose because, i.e., they cannot be translated, those could be copied "as-is". * The others are things you don't know the translation for, or it's unclear. For those, if you copy the msgid over then you can't distinguish those from the ones above. That for the first ones, msgid's should be copied over msgstr and leave them *as translated*. For the other ones, the right thing to do seems to be leaving the msgstr blank, or either mark the translation as fuzzy (whatever you prefer, gettext will ignore both). So future translators and gettext know that those string are *not* translated. Do you Agree? If so, there are some translations that have to remove strings :) On related news, a *complete* translation of Django is formed of 882 translated strings and 92 untranslated. From those 92 a bunch come from localflavour ;) Yours, Marc PS: Thanks for discussing the issue, translations would be boring without debating over msgstrs!! -- http://www.marcfargas.com -- will be finished some day.
signature.asc
Description: Esta parte del mensaje está firmada digitalmente
