Merge lp:~mterry/duplicity/utf8-po into lp:duplicity/0.6
Proposed by
Michael Terry
Status: | Merged |
---|---|
Merged at revision: | 863 |
Proposed branch: | lp:~mterry/duplicity/utf8-po |
Merge into: | lp:duplicity/0.6 |
Diff against target: |
92 lines (+43/-4) 5 files modified
bin/duplicity (+1/-1) bin/rdiffdir (+1/-1) duplicity/__init__.py (+1/-1) testing/manual/config.py.tmpl (+1/-1) testing/tests/unicode.py (+39/-0) |
To merge this branch: | bzr merge lp:~mterry/duplicity/utf8-po |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
duplicity-team | Pending | ||
Review via email: mp+124209@code.launchpad.net |
Description of the change
For some crazy reason, the gettext module defaults to giving you strings in whatever charset the po file happened to define. Which means you never know what string of bytes you're going to get.
This module makes sure we always get utf-8 byte strings. So we're at least predictable and reduces one source of UnicodeDecodeErrors (like in bug 989496)
To post a comment you must log in.