bugGNU gettext - Bugs: bug #33298, Explicit translated flag


bug #33298: Explicit translated flag

Submitted by:  None
Submitted on:  Wed 11 May 2011 11:52:11 PM UTC  
Category: NoneSeverity: 3 - Normal
Item Group: NoneStatus: None
Privacy: PublicAssigned to: None
Open/Closed: Open

Add a New Comment (Rich MarkupRich Markup):

You are not logged in

Please log in, so followups can be emailed to you.


Wed 11 May 2011 11:52:11 PM UTC, original submission:

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.



(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach File(s):

No files currently attached


Depends on the following items: None found

Items that depend on this one: None found


CC list is empty


Do you think this task is very important?
If so, you can click here to add your encouragement to it.
This task has 0 encouragements so far.

Only logged-in users can vote.


Please enter the title of George Orwell's famous dystopian book (it's a date):



No Changes Have Been Made to This Item

Back to the top

Powered by Savane 3.1-cleanup