#26093: makemessages messes up unicode characters on Python 3
--------------------------------------+---------------------
Reporter: sephii | Owner: nobody
Type: Bug | Status: new
Component: Internationalization | Version: 1.9
Severity: Normal | Keywords: python3
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+---------------------
If you run the makemessages command on Python 3 (tested on Python 3.4.2,
Django 1.9.1) and you have strings that contain unicode characters they
will get incorrectly escaped or even stripped out from the generated PO
file.
For example in a template with {% trans "hello world" %} (the space here
is the unicode character 202f), you'll end up with an msgid
"hello\\u202fworld", which makes the original string unrecognized as a
translation key. Trying with the non-breaking space character (00a0) makes
it disappear completely and creates an msgid "helloworld".
The same works fine on Python 2, the unicode characters are preserved in
the resulting PO file.
--
Ticket URL: <https://code.djangoproject.com/ticket/26093>
Django <https://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 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].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/049.39f54036ebe1daf852d971e4190ae971%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
