This is the mail archive of the
mailing list for the glibc project.
Re: EUC-KR and WON SIGN
- To: Paul Eggert <eggert at twinsun dot com>
- Subject: Re: EUC-KR and WON SIGN
- From: Jungshik Shin <jshin at pantheon dot yale dot edu>
- Date: Tue, 7 Nov 2000 16:17:56 -0500 (EST)
- cc: drepper at cygnus dot com, libc-alpha at sources dot redhat dot com
- Reply-To: jshin at pantheon dot yale dot edu
On Tue, 7 Nov 2000, Paul Eggert wrote:
> From: Ulrich Drepper <email@example.com>
> Date: 07 Nov 2000 12:42:34 -0800
> > It was brought into my attention that recent snapshots of glibc has \0x5c
> > in EUC-KR mapped to U20A9 instead of U005C.
> This was done on request of some Korean people. Now you are telling
> me again the opposite is what you expect.
> I'm sick of this. Either you all get to the same conclusion or it
> will stay as it is.
> You will never get complete consensus on this issue, as it is a
> contentious one. The best you can expect is a majority opinion.
> As I wrote earlier, the majority opinion is to treat 0x5c as a
> backslash in EUC-JP. I think EUC-KR is similar, though I haven't
> surveyed implementations there.
You're right. As I wrote before, in Unix/X11 world \0x5c has been almost
always U005C. MS-Windows uses UHC(Windows-949) which can be dealt with
separately from EUC-KR.
> I don't know why glibc recently
> changed away from the majority opinion for the EUC encodings.
That's exactly what I meant at the end of my first message on the issue
JS> I guess this is also in line with what has been done for EUC-JP and SJIS
JS> (CP94?) pair and EUC-CN and CP950(?) pair in glibc.