Ramiro mentioned this in his earlier email, but I wanted to make sure people noticed.
Three strings that were publicly visible were not marked for translation and were discovered yesterday. Since these are entirely *new* strings, not changes of existing strings, we have added ugettext() calls around them. If you do nothing after this addition, your translation will not be harmed. Previously translated strings will not suddenly move to "fuzzy" or anything. But if you're going for 100% (and your users will like it if you do), there are a couple of extras now. The 1.0 release is still scheduled for next Tuesday. We are in string freeze at the moment, which means no changes to existing strings, so you can translate the existing strings and feel comfortable that your hard work will not be undone in the next few days. Good luck! Regards, Malcolm --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
