Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

poparser wrongly parses first unit source #3450

Closed
nijel opened this issue Jun 20, 2016 · 2 comments
Closed

poparser wrongly parses first unit source #3450

nijel opened this issue Jun 20, 2016 · 2 comments

Comments

@nijel
Copy link
Member

nijel commented Jun 20, 2016 •
edited

When msgid of first unit of po file is unicode, it's wrongly parsed (it's decoded using iso-8859-1 instead of charset specified in the header).

File which shows this behavior: Author_Group.po.txt

Testcase patch to see the problem: test_po.patch.txt
@nijel nijel mentioned this issue Jun 22, 2016
Closed
@nijel
Copy link
Member Author

nijel commented Jun 22, 2016

There is PR for this: #3455

@dwaynebailey
Copy link
Member

Fixed in #3455

@nijel nijel mentioned this issue Jul 19, 2016
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix parsing of Gettext po files with first entry in unicode
2 participants
@nijel @dwaynebailey