#3923: [unicode] make-messages.py does not work well with unicode strings
---------------------------+------------------------------------------------
   Reporter:  mtredinnick  |                Owner:  mtredinnick         
     Status:  closed       |            Component:  Internationalization
    Version:  SVN          |           Resolution:  wontfix             
   Keywords:               |                Stage:  Accepted            
  Has_patch:  0            |           Needs_docs:  0                   
Needs_tests:  0            |   Needs_better_patch:  0                   
---------------------------+------------------------------------------------
Comment (by [EMAIL PROTECTED]):

 I've found a strange make-messages.py/xgettext behaviour: make-
 messages.py/xgettext is able to extract utf8-strings from *one* file! But
 as soon as there are *more than one* files to process, make-
 messages.py/xgettext fails.
 
 This problem has something to do with the way of xgettext being called:
 When a pot file already exists (e. g. if xgettext is called on the
 *second* file to be processed), xgettext is called with the "--omit-
 header" option... and will fail on utf8 encoded files. Without "--omit-
 header" the message extraction is working alright.
 
 Maybe make-messages.py could be changed to regard this, so one could use
 utf8 encoded messages for translation?
 
 Translation of utf8 encoded strings seems to work without problems...

-- 
Ticket URL: <http://code.djangoproject.com/ticket/3923#comment:11>
Django Code <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