On Wed, Jun 18, 2008 at 3:05 AM, Marc Fargas <[EMAIL PROTECTED]> wrote: > El mar, 17-06-2008 a las 21:47 -0300, Ramiro Morales escribió: > > [snip] > >> 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? > > Because then the human could not distinguish really translated things > from things that were not translated for some reason.
How about this? * translated entries have a non-empty msgstr (including when msgid == msgstr) * entries that need more work are marked fuzzy * untranslated entries have an empty msgstr It's clear what the state of every entry is, msgfmt --statistics reports are correct and ITSM that this is the way things are intended to work. Arien --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django I18N" group. To post to this group, send email to [email protected] 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 -~----------~----~----~----~------~----~------~--~---
