[issue19907] gettext - Non ascii chars in header

2017-11-09 Thread Serhiy Storchaka
Change by Serhiy Storchaka : -- resolution: -> out of date stage: -> resolved status: pending -> closed ___ Python tracker

[issue19907] gettext - Non ascii chars in header

2017-09-22 Thread Serhiy Storchaka
Changes by Serhiy Storchaka : -- status: open -> pending ___ Python tracker ___

[issue19907] gettext - Non ascii chars in header

2015-04-15 Thread Michael McFadden
Michael McFadden added the comment: This might be fixed by issue17156, which would explain why I can't recreate it. https://github.com/python/cpython/commit/f4273cfd16fa502f0eb8a0a8fd1c537ec63e47db -- ___ Python tracker rep...@bugs.python.org

[issue19907] gettext - Non ascii chars in header

2015-04-15 Thread Michael McFadden
Michael McFadden added the comment: issue18128 is not related methinks. This ticket: POT-Creation-Date issue18128: PO-Revision-Date -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue19907

[issue19907] gettext - Non ascii chars in header

2015-04-13 Thread Michael McFadden
Michael McFadden added the comment: I'm having no luck reproducing this issue. Regarding pygettext.py generating .po files: I've used the messages.po file provided by the OP, and also using a generated .po file from pygettext.py with the offending header PO-Revision-Date: As a side note, I'm

[issue19907] gettext - Non ascii chars in header

2013-12-10 Thread Jakub Wilk
Jakub Wilk added the comment: See also issue18128. Date headers are not only for humans; I've seen software that parses them. -- nosy: +jwilk ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue19907

[issue19907] gettext - Non ascii chars in header

2013-12-06 Thread Michael Müller
New submission from Michael Müller: When having non ascii chars in the header of an translation file (xxx.po) the following error will be raised: File D:\Python33\lib\gettext.py, line 410, in translation t = _translations.setdefault(key, class_(fp)) File D:\Python33\lib\gettext.py,

[issue19907] gettext - Non ascii chars in header

2013-12-06 Thread Éric Araujo
Éric Araujo added the comment: It looks like there are two issues here. First, what would be a correct format for the PO-Revision-Date line? (human-readable string or numerical timezone) Second, gettext supports UTF-8 for the po file, which should support ä without problem, so maybe

[issue19907] gettext - Non ascii chars in header

2013-12-06 Thread Michael Müller
Michael Müller added the comment: Used encoding is utf-8. Testfile I used added to this comment. Second about the PO-Revision-Date: It should be human readable. It's unimportant for the program itself - it's used for the translator of the xxx.po file. Normally the whole header could be removed