May be it would better to post this to "Django developers" mailing list?
пятница, 30 мая 2014 г., 15:53:56 UTC+3 пользователь Андрей Меньков написал:
-- пятница, 30 мая 2014 г., 15:53:56 UTC+3 пользователь Андрей Меньков написал:
Django management command doesn't recognize multiline strings as strings to localize. So such strings don't appear in resulting django.po files after running commandFor example for such a string{code}{{ _(''' fhsdafjkshdfjkasdhfksjytyerwtuiwyertuiywert''') }}{code}I might be the bug of GNU xgettext utility, because makemessages uses it to produce *.po files, but after running xgettext I became sure that the problem is in the makemessages command, not xgettext.I ran xgettext using the following commandxgettext --keyword=gettext_noop --keyword=gettext_lazy --keyword=ngettext_lazy:1,2 --keyword=ugettext_noop --keyword=ugettext_lazy --keyword=ungettext_lazy:1,2 --keyword=pgettext:1c,2 --keyword=npgettext:1c,2,3 --keyword=pgettext_lazy:1c,2 --keyword=npgettext_lazy:1c,2,3 --from-code UTF-8 --add-comments=Translators --from-code utf-8 -d django -p ./output_dir -L Python temp_i18n_template.html
After running this command I got file output_dir/django.po with specified string inside it.What I can do now? What do you think about this "bug" ?
P.S. It's my first attempt to contribute to Django somehow. So please do not judge strictly). I haven't found anywhere about this problem and about its' fixes too.
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/565e7448-bdc8-4b60-8f59-ab8d13d2eb34%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
No comments:
Post a Comment