Opened 17 years ago
Closed 17 years ago
#7030 closed (fixed)
Allow non-ASCII characters in input for translation for multiple Javascript files
Reported by: | anonymous | Owned by: | nobody |
---|---|---|---|
Component: | Internationalization | Version: | dev |
Severity: | Keywords: | ||
Cc: | Triage Stage: | Unreviewed | |
Has patch: | yes | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
make-messages.py doesn't work well for input file containing UTF-8 strings to translate when you have multiple javascript files to translate
cd project_dir copy test.js to template directory # run make_messages # python /opt/django-0.97_pre7403/django/bin/make-messages.py -a -d djangojs processing language fr
everything is fine
Problem occures when you have multiple JS file to translate:
copy test2.js to template directory # run make_messages # python /opt/django-0.97_pre7403/django/bin/make-messages.py -a -d djangojs processing language fr errors happened while running xgettext on test2.js pl:2: warning: The following msgid contains non-ASCII characters. This will cause problems to translators who use a character encoding different from yours. Consider using a pure ASCII msgid instead. déjeuner pl:2: invalid multibyte sequence pl:2: invalid multibyte sequence pl:2: invalid multibyte sequence pl:2: invalid multibyte sequence
with patched version :
# python /opt/django-0.97_pre7403/django/bin/make-messages.py.patched -a -d djangojs processing language fr
Attachments (3)
Change History (4)
by , 17 years ago
by , 17 years ago
Attachment: | make-message.patch added |
---|
make-messages.py patch to deal with JS files as .html files (no use of omit-header) and stripping header if .pot file exists
comment:1 by , 17 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
Javascript file #1 for testing purpose