412597 - Use proper Gettext PO files

Status: RESOLVED WONTFIX

(addons.mozilla.org Graveyard :: Localization, defect)

Description

[Dwayne Bailey]

Please change the current hacked Gettext PO files to use proper PO files.

i.e.
msgid "some_id"
msgstr "Translate this"

to:
msgid "Translate this"
msgstr "Vertaal hierdie"

The current method is not recommended as it loses all the value of the PO format including:
1) The ability to update translations correctly
2) Makes it impossible to use good PO editing tools
3) You cannot use existing Translation Memory

I know coders love this way as it seems easier to them, but to translators it eliminates all the value.  And this is done for translators right? ;)

Comment 1

[Fred Wenzel [:wenzel]]

I am sorry, but at least for AMO, this is a WONTFIX. The current gettext msgid style is there for a reason; as a matter of fact it is not more convenient for the coders to use tags, instead we'd like to use plain English too.

However, if we did that, every correction of a typo or punctuation or slight differences in wording in the English file would lead to unnecessary work for all localizers.

Therefore, we decided to push the English wording into all other locale's .po files initially, for the localizers to translate. They are initially marked fuzzy, so that they are easy to find: Whenever a localizer needs to update newly added strings, he or she can just use his preferred (PO-)editor to find and translate these strings.

If you have additional questions about the procedure, please let us know.

Comment 2

[Dwayne Bailey]

I honestly don't understand your reasoning.  Especially since this style has not made it easier for programmers.

For the minor irritation of seeing all corrections in English I lose the following features from my PO editor.

1) The ability to pull in text from my previous translations since now I have no idea what to match
2) I can't run any validation checks that compare msgid to msgstr
3) Ability to find terminology in the msgid and make sure I've applied correct rules to the msgstr

Sure by your logic I can still translate.  But you've taken my preferred PO editor and turned it into a text editor.  Translators have lost all the valuable features that ensure quality and consistency for the misguided benefit that they now don't have to see changes to the English.  

Essentially you've made our work harder. Tragic.

Comment 3

[Fred Wenzel [:wenzel]]

(In reply to comment #2)
> 1) The ability to pull in text from my previous translations since now I have
> no idea what to match

This is true, however our localizers have established many times that re-using text is not acceptable. A string that would simply be called "Firefox" may lead to grammatical mistakes when re-used in other parts of the site. Message tags as used by us avoid this, plain English does not.

> 2) I can't run any validation checks that compare msgid to msgstr

This is correct, however if you only remove the fuzzy tag once something is translated, you should be golden.

> 3) Ability to find terminology in the msgid and make sure I've applied correct
> rules to the msgstr

I don't understand this, I am sorry. Do you mean having enough "%s" tags in a message string?

> Sure by your logic I can still translate.  But you've taken my preferred PO
> editor and turned it into a text editor.  Translators have lost all the
> valuable features that ensure quality and consistency for the misguided benefit
> that they now don't have to see changes to the English.  

I hope now you understand the reasoning a little better. Essentially it is not about keeping people from seeing changes to the English localization. Instead it is about avoiding the inappropriate reusing of strings along with breaking the English-centered localization that leads to the aforementioned problems with, for example, minor spelling changes.