On Tue, Jun 17, 2008 at 9:13 PM, Marc Fargas <[EMAIL PROTECTED]> wrote:
> Hi people,
>
> I just came accros changeset [7682] and wanted to remind you to *please*
> do not mark as translated string which are kept in English.
>
> I mean, if i.e. You do not translate a word, or cannot translate it for
> some reason (like strings in localflavour) *please* leave the msgstr
> *blank* do not copy the msgid over msgstr as this makes it harder to
> know what is really translated and what not.
>
> If msgstr's are left blank Django will use the msgid as is the string
> was unstralated, which is fine ;)
>

Actually, I have been suggesting exactly the opposite, look in this list
archives for a couple of examples.

Two points in favor of copying the msgid value over the msgstr:

1. It actually indicates the fact somebody (another member of a translation
   team, yourself) has already reviewed that specific entry and has decided
   that the value should be copied verbatim from msgid to msgstr. If you find
   a

   msgstr ""

   there is now way you can if it was left empty on purpose or not. No GNU
   gettext tools creates .po files with these valued automatically copied
   for you.

2. It skews statistics (the ones you get with msgfmt --statistics) because
   in these results an empty msgstr counts as a unstranslated literal.
   In the case the translator decided the msgstr value should be equal to the
   msgid value, leaving the latter empty means that translations will never
   reach 100%.

I guess the real logic behind this reasoning is: If the final string that
the end user is going to see is the same, why not mark it explicitely
on the .po file for the benefit of both human and gettext tools?

CouldnĀ“t find any documentation suggesting one practice over the other. Is
there any experienced translator that can share his thoughts about the
matter?.

Regards,

--
 Ramiro Morales

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Django I18N" group.
To post to this group, send email to Django-I18N@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/Django-I18N?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to