Opened 4 years ago
Closed 4 years ago
#31302 closed Cleanup/optimization (invalid)
A lot of messages become untranslated after #30400 (typographic improvement)
| Reported by: | rad164 | Owned by: | nobody |
|---|---|---|---|
| Component: | Uncategorized | Version: | 3.0 |
| Severity: | Normal | Keywords: | |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
#30400 converts ASCII quotes and punctuations into unicode ones in user facing strings. But it causes many missing translations.
Some locales has been updated after the conversion and have unicode quotes. But the rest are untouched and still have ascii quotes in msgid. As a result, these locales seems to be '100% translated' on transifex but shows English message at many places because they know 'Added {name} "{object}".' but does not know 'Added {name} “{object}”.' for example.
Of course, the issues should be finally solved in each translation teams. For example, some language uses different quotes (« in fr, 「 in ja).
But isn't it better to convert them at once as quick fix?
Here is some of my ideas.
- Get updated msgid in [42b9a232] and replace them in each .po files machinery. Keep msgstr untouched. Then the user can see many messages in their native languages again. But it is hard for translators to track changes.
- Update .pot / .po files and let gettext do fuzzy-matching. The messages are still shown in English because of fuzzy flags, but translators will easily find and fix them.
- Replace all ascii punctuations with unicode ones both in msgid and msgstr in all .po files. (maybe too offensive)
- Just nudge translators to handle the changes.
Sorry, we knew that this change was going to give translators some work, but translators had several weeks to translate them for 3.0, and even for 3.0.3. And as a translator myself, I can tell you that updating those strings should not take much than 30 minutes on Transifex.
I have strong doubts about your affirmation that:
It could be the case if translators did their work after January 31st, but otherwise it shouldn't happen (and if it does, create a specific ticket with example language/code).
I am against pushing ourselves changes in .po files, as this is the realm of translators and it should stay so.