2,569
edits
Changes
Jump to navigation
Jump to search
Line 146:
Line 146: − Testing Pootle I have found a few issues. I will try to describe. − + +
→UTF-8
== Pootle issues==
== Pootle issues==
=== UTF-8 ===
=== UTF-8 ===
Bug created, 'Use UTF-8 for console .po files'
Bug created, 'Use UTF-8 for console .po files'
http://bugs.contribs.org/show_bug.cgi?id=3858
http://bugs.contribs.org/show_bug.cgi?id=3858
Testing Pootle I have found a few issues. I will try to describe.
Pootle (and Translation Toolkit used by Pootle) use as default a charset UTF-8. Everytime I have create a new language translation, Pootle parse from templates encoding as UTF-8. Everytime I have "Update from templates" the target PO files are updated as UTF-8, and if target has set charset=iso-8859-1, it is then corrupted. I can't found a method to set Pootle to use ISO-8859-1 as default. Because this, and to avoid these issues I have decide to use UTF-8 as charset in Pootle. Please see http://translate.sourceforge.net/wiki/guide/locales/glibc?s=charset#editing
Pootle (and Translation Toolkit used by Pootle) use as default a charset UTF-8. Everytime I have create a new language translation, Pootle parse from templates encoding as UTF-8. Everytime I have "Update from templates" the target PO files are updated as UTF-8, and if target has set charset=iso-8859-1, it is then corrupted. I can't found a method to set Pootle to use ISO-8859-1 as default. Because this, and to avoid these issues I have decide to use UTF-8 as charset in Pootle. Please see http://translate.sourceforge.net/wiki/guide/locales/glibc?s=charset#editing