Hi Marc, > App A (English, Catalan, German) > App B (English, German) > App C (English) > > So what happens when we execute "python manage.py makemessages -a"?
Why not go a step further and let makemessages take an optional list of apps (e.g. AppCommand) that will specifically be looked at. That would allow us to make sure we don't miss some strings from globally installed apps (e.g. via package manager) when creating a project catalog. > More complicated would be if one application is partially translated > to a language. What to do in that case? Consider that the application > is translated? Consider that it's not? Add to our project catalog just > the strings that are not translated? Ideally the partially translated app catalogs should be added to the project catalog. Although that would require a sense of what is actually in those files. > IMHO I would prefer to keep it simple, and just ignore applications > having a locale directory. Of course it'll be more work for developers > who will have to create catalogs for missing languages in localized > applications. And of course it'll be a problem if you don't have write > permissions on the application. But I think that is better for > (project) developers spending few time on creating some catalogs, than > on figure out how things work (or why things don't work as they > expect). > One thing I'm considering, is if it would it be worth creating a > parameter for the makemessages command (like --no-ignore) to force the > inclusion of all strings on the project catalog. Adding that feature seems worthwhile, adding a flag to disable it even better. Jannis --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
