#9753: makemessages failed on long Chinese text
-------------------------------------------+--------------------------------
          Reporter:  Will                  |         Owner:  nobody             
         
            Status:  new                   |     Milestone:  post-1.0           
         
         Component:  Internationalization  |       Version:  1.0                
         
        Resolution:                        |      Keywords:  django-admin.py 
makemessages
             Stage:  Unreviewed            |     Has_patch:  0                  
         
        Needs_docs:  0                     |   Needs_tests:  0                  
         
Needs_better_patch:  0                     |  
-------------------------------------------+--------------------------------
Comment (by mtredinnick):

 Ah, another windows problem. Fantastic. :-(

 A couple of comments:
  1. The reason we don't have `--no-wrap` on unconditionally is that it
 leads to pretty ugly PO files, particularly for those working in text
 editors. However, it's becoming clear that there's a need to allow
 arbitrary gettext options to be specified and passed through our wrappers
 to xgettext, with `--no-wrap` being one of those things. With luck, we'll
 get that change in for 1.1.
  2. We mark the template files as being of type "Python" because the
 conversion process to the intermediate form that we ultimately run
 xgettext over converts variables to Python format strings (not valid for
 `{% trans %}`, but certainly so for `{% blocktrans %}` tags). The
 advantage of doing that is that translation tools know about Python format
 and can mark them appropriately (e.g. syntax highlighting) and
 `compilemessages` will warn about any misspellings of format strings, or
 omitted format strings. That catches a ''lot'' of errors. If the gettext
 tools somehow magically knew about Django markup, we'd use "Django"
 format, but that isn't the case today, so the conversion to intermediate
 Python format, which is then processed with xgettext is actually a pretty
 neat way of working with existing tools for translators.

 If the original poster can confirm this is just a problems with an older
 gettext on Windows then the resolution is to upgrade to a more recent
 version of gettext (it's been over 2 years since gettext 0.15 was
 released, so we're not requiring anything that's just been released in the
 last few months) and, in the future, we'll also allow the arbitrary
 parameter passing.

-- 
Ticket URL: <http://code.djangoproject.com/ticket/9753#comment:3>
Django <http://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Django updates" 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-updates?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to