Hi Maciej, Thanks for your suggestion. This is nearly the kind of thing that I wanted to do. But if I am not mistaken, makemessages cannot capture expanded messages, since it analyses the code when it is not running, so it cannot predict what will be expanded. So it seems to me that changing the gettext calls in this way would break the standard translation workflow with makemessages/compilemessages. This way the whole idea starts to look more complicated than alternative solutions.
Perhaps a new variant of the gettext function could offer the desired behavior in the translation step, while avoiding breaking things in the makemessages step. I will look into this and post an update if I have any success. Best, Strahinja -- You received this message because you are subscribed to the Google Groups "Django internationalization and localization" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/django-i18n. For more options, visit https://groups.google.com/d/optout.
