>> 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.
Kbabel has the option to show you all the strings that have the same msgstr and msgid, under "Tools->Validation->Translations Containing English". So you or some other translator can review your choices and why they were left in English anytime. And the statistics say that it's 100% translated. Everybody is happy. :) So, I also think that it's better to copy msgid to msgstr when the translator can't decide or when there is no point to translate something. -- Glisha --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
