Red Hat Bugzilla – Bug 40657
Bad multibyte chars in japanese .po-file
Last modified: 2007-04-18 12:33:15 EDT
[lynx-2.8.4-12.src.rpm] Description of Problem: lynx can not be rebuilt because msgfmt fails on po/ja.po. Steps to Reproduce: 1. LANG=C rpm --rebuild lynx-2.8.4-12.src.rpm Actual Results: ... file=./`echo ja | sed 's,.*/,,'`.gmo \ && rm -f $file && PATH=../src:$PATH /usr/bin/msgfmt -o $file ja.po ja.po:568: invalid multibyte sequence ja.po:569: end-of-line within string ... ja.po:3906: end-of-line within string too many errors, aborting make[1]: *** [ja.gmo] Error 1 Additional Information: $ rpm -q gettext glibc gettext-0.10.37-2 glibc-2.2.2-10 $LINGUAS is unset
This compiled with an older gettext... Did gettext switch to a different encoding?
Bug #40656 tells some details and a possible workaround (OLD_PO_FILE_INPUT=yes).
That can't be blindly used, since I don't know ow a proper way to identify whether or not the format is old or new... I'm still waiting on feedback from the Japanese office on how to do that.
OK, we're going for the OLD_PO_FILE_INPUT.