gettext: Untranslated Entries

1 
1 8.3.7 Untranslated Entries
1 --------------------------
1 
1    When ‘xgettext’ originally creates a PO file, unless told otherwise,
1 it initializes the ‘msgid’ field with the untranslated string, and
1 leaves the ‘msgstr’ string to be empty.  Such entries, having an empty
1 translation, are said to be "untranslated" entries.  Later, when the
1 programmer slightly modifies some string right in the program, this
1 change is later reflected in the PO file by the appearance of a new
1 untranslated entry for the modified string.
1 
1    The usual commands moving from entry to entry consider untranslated
1 entries on the same level as active entries.  Untranslated entries are
1 easily recognizable by the fact they end with ‘msgstr ""’.
1 
1    The work of the translator might be (quite naively) seen as the
1 process of seeking for an untranslated entry, editing a translation for
1 it, and repeating these actions until no untranslated entries remain.
1 Some commands are more specifically related to untranslated entry
1 processing.
1 
1 ‘u’
1      Find the next untranslated entry (‘po-next-untranslated-entry’).
1 
1 ‘U’
1      Find the previous untranslated entry
1      (‘po-previous-untransted-entry’).
1 
1 ‘k’
1      Turn the current entry into an untranslated one (‘po-kill-msgstr’).
1 
1    The commands ‘u’ (‘po-next-untranslated-entry’) and ‘U’
1 (‘po-previous-untransted-entry’) move forwards or backwards, chasing for
1 an untranslated entry.  If none is found, the search is extended and
1 wraps around in the PO file buffer.
1 
1    An entry can be turned back into an untranslated entry by merely
1 emptying its translation, using the command ‘k’ (‘po-kill-msgstr’).
1 ⇒Modifying Translations.
1 
1    Also, when time comes to quit working on a PO file buffer with the
1 ‘q’ command, the translator is asked for confirmation, if some
1 untranslated string still exists.
1