msgmerge destroys some input strings in japanese and korean .po files.
A way to reproduce this, is to create this string in an input file: "i".
In my case the input files are in ISO-8859-1. After running msgmerge all
po files get updated ok, unless ko.po and ja.po where this string gets
changed to: "i\0" where the "0" is a zero byte (\0).
The problem seems to be this patch:
$ rpm -q gettext
Do you have any specific examples?
Nakai, this is the patch you added to make it handle Japanese properly... could
you look into this?
That input string were supposed to consist of the letter "e with acute" (0xe9)
Nakai believes this no longer to be a problem with gettext 0.10.37 and above,
currently in Rawhide. Open if this is still a problem.