Changes between Version 2 and Version 3 of Ticket #18183, comment 2


Ignore:
Timestamp:
01/18/2013 07:48:11 PM (3 years ago)
Author:
ramiro
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #18183, comment 2

    v2 v3  
    1 AFAIK the header is an otherwise normal translatable literal (and a multi-line one that's why it starts with a `msgstr ""` line).
     1AFAIK the header is an otherwise normal translatable literal (a multi-line one that's why it starts with a `msgstr ""` line).
    22
    3 The `#, fuzzy` marker isn't put there by the Django wrapper but by the official GNU gettext tools which we use at the low level. The markers are put when PO files are created for the first time because some fields of the header are prefilled but there are others that need intervention of a translator, so it is in a incomplete state.
     3The `#, fuzzy` marker isn't put there by the Django wrapper but by the official GNU gettext tools which we use at the low level. The markers are added when PO files are created for the first time because some fields of the header are prefilled but there are others that need intervention of a translator, so it is in a incomplete state.
    44
    5 The translator (or the translation tools she/he uses) is supposed to remove them once she updates the fields of the header contained in such `msgstr`.
     5The translator (or the translation tools she uses) is supposed to remove them once she updates the fields of the header contained in such `msgstr`.
    66
    77The header needs to be completed by the translator because otherwise the `msgfmt(1)` GNU gettext tool will emit warning/errors when trying to convert them to `.mo` files.
Back to Top