Description of problem: Some time recently I started seeing the arabic yeh barree character ے being inserted into my Norwegian bokmål translations for GNOME instead of the actual other octal escaped UTF-8 chars are in the source files. I'm guessing xgettext has problems for some reason. I tried running intltool-update using LC_ALL=C to see if it was locale related, but that gave the same result. Version-Release number of selected component (if applicable): [kmaraas@localhost po (master *)]$ rpm -q gettext gettext-0.19.2-2.fc21.x86_64 [kmaraas@localhost po (master *)]$ rpm -q intltool intltool-0.50.2-8.fc21.noarch [kmaraas@localhost po (master *)]$ How reproducible: Every time. Steps to Reproduce: 1. run intltool-update -p in a module that has C octal escaped UTF-8 chars in the source code 2. check the resulting .pot file 3. Actual results: Expected results: Additional info:
Thanks for the report. Pushed a fix with a test: http://git.savannah.gnu.org/cgit/gettext.git/commit/?id=883001928eacb62fdf2a5c7da0f38e08148b0fcf http://git.savannah.gnu.org/cgit/gettext.git/commit/?id=5f977a30e51b58540aee58e9f170c42bd5e88502 Will make another bug-fix release shortly and update the package.
Any chance of an updated package with this fix in Fedora 21?
gettext-0.19.2-4.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/gettext-0.19.2-4.fc21
Since it seems important for translators, I've built it for F21 at first. Not sure if it could be a blocker, but at least it could be a zero-day update.
Package gettext-0.19.2-4.fc21: * should fix your issue, * was pushed to the Fedora 21 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing gettext-0.19.2-4.fc21' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-12158/gettext-0.19.2-4.fc21 then log in and leave karma (feedback).
gettext-0.19.2-4.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.