Bug 40972

Summary: msgmerge corrupts input strings in korean and japanese po files
Product: [Retired] Red Hat Linux Reporter: Håvard Kvålen <havardk>
Component: gettextAssignee: Trond Eivind Glomsrxd <teg>
Status: CLOSED RAWHIDE QA Contact: Aaron Brown <abrown>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.1CC: ynakai
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2001-05-16 20:21:24 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Håvard Kvålen 2001-05-16 20:13:19 UTC
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:
gettext-0.10.35-oka-plus.patch

$ rpm -q gettext
gettext-0.10.35-31

Comment 1 Trond Eivind Glomsrxd 2001-05-16 20:17:52 UTC
Do you have any specific examples?

Nakai, this is the patch you added to make it handle Japanese properly... could
you look into this?

Comment 2 Håvard Kvålen 2001-05-16 20:21:19 UTC
That input string were supposed to consist of the letter "e with acute" (0xe9)

Comment 3 Trond Eivind Glomsrxd 2001-06-04 14:04:11 UTC
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.