Code

Changes between Initial Version and Version 1 of Ticket #18183, comment 2


Ignore:
Timestamp:
04/20/12 08:34:07 (2 years ago)
Author:
ramiro
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #18183, comment 2

    initial v1  
    1 AFAIK the header is a otherwise normal translatable literal (and a multi-line one that's why it starts with a `msgstr ""` line) the `#, fuzzy` marker isn't put there by the Django wrapper but by the official GNU gettext tools which we use at 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 other that need intervention of a translator, so  it is in a incomplete state. 
     1AFAIK the header is a otherwise normal translatable literal (and a multi-line one that's why it starts with a `msgstr ""` line). The `#, fuzzy` marker isn't put there by the Django wrapper but by the official GNU gettext tools which we use at 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. 
    22 
    3 The translator (or the translation tools she/he uses) is supposed to remove them once the use updates the fields of the header contained in such `msgstr`. 
     3The 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`. 
    44 
    5 The header needs to be completed by the translator because otherwise the `msgfmt(1)` GNU gettext tool will emit warning/errors when tryin to convert them to `.mo` files. 
     5The 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.