GNU gettext - Bugs: bug #33298, Explicit translated flag
You are not allowed to post comments on this tracker with your current authentication level.
bug #33298: Explicit translated flag
Submitter: | None | ||
Submitted: | Wed 11 May 2011 11:52:11 PM UTC | ||
Category: | Other | Severity: | 3 - Normal |
Item Group: | None | Status: | None |
Privacy: | Public | Assigned to: | None |
Open/Closed: | Open |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
Carbon-Copy List
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follows 1 latest change.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2016-11-27 | haible | Category | None | ![]() |
Other |
PO assumes that a non empty string is translated and that fuzzy can specify whether a string should be included in generated files.
Since there is no explicit translated or untranslated marking we find the following possible problems:
#. Set this to "yes" for RTL languages or leave untranslated
msgctxt "RTL"
msgid ""
msgstr ""
This is untranslated and will remain untranslated for an LTR language.
A programmer could specify that someone should use "yes" or "no" but often they don't.
I would like to suggest adding an explicit marker for this case to ensure that this case is unambiguous.
#, translated
Can be used to explicitly mark a unit as translated.