Bug 9833 - wrong "noexpr" in ko_KR LC_MESSAGES data
Summary: wrong "noexpr" in ko_KR LC_MESSAGES data
Status: RESOLVED FIXED
Alias: None
Product: glibc
Classification: Unclassified
Component: localedata (show other bugs)
Version: unspecified
: P2 normal
Target Milestone: ---
Assignee: GNU C Library Locale Maintainers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-02-10 16:00 UTC by Changwoo Ryu
Modified: 2014-07-01 20:55 UTC (History)
1 user (show)

See Also:
Host:
Target:
Build:
Last reconfirmed:
fweimer: security-

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Changwoo Ryu 2009-02-10 16:00:26 UTC 
$ locale LC_MESSAGES
^[yY¿¹]
^[nN¾Æ´Ï¿À]


UTF-8
$

The word in the second line, "¾Æ´Ï¿À" is the negative answer in Korean. But only
the first character "¾Æ" should be in the brackets, to make it work as written
in the locale data:

...
% NOTES on LC_MESSAGES
%
% Any string starting with any form of Latin Y and Korea
% `Yea' are recognized as affirmative answer.  Negative answer is
% recognized by Latin N and Hangul `A' (which stands for ``Anio'').

LC_MESSAGES

yesexpr "<U005E><U005B><U0079><U0059><UC608><U005D>"

noexpr  "<U005E><U005B><U006E><U004E><UC544><UB2C8><UC624><U005D>"

END LC_MESSAGES
...


noexpr should be like this:

noexpr  "<U005E><U005B><U006E><U004E><UC544><U005D>"
Comment 1 Ulrich Drepper 2009-03-15 20:36:04 UTC 
I've changed the data in cvs.  I added a definition of the nostr field since
that's what you said is spelled out.  If you want. provide a definition of the
yesstr.
Comment 2 Changwoo Ryu 2009-03-15 21:43:19 UTC 
yesstr "<UC608>:<UB124>"

"³×"(U+B124, NE) is a synonym of "¿¹"(U+C608, YE).