This is the mail archive of the libc-alpha@sources.redhat.com mailing list for the glibc project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [PATCH] Remove 0x005C conversion from __jisx0208_from_ucs4_lat1 for ISO-2022-JP

From: Petter Reinholdtsen <pere at hungry dot com>
To: libc-alpha at sources dot redhat dot com
Cc: ukai at debian dot or dot jp
Date: Fri, 10 Sep 2004 08:32:52 +0200
Subject: Re: [PATCH] Remove 0x005C conversion from __jisx0208_from_ucs4_lat1 for ISO-2022-JP
Bcc: Petter Reinholdtsen <petter dot reinholdtsen at usit dot uio dot no>
References: <811xib64v6.wl@omega.webmasters.gr.jp> <81vfenqv1u.wl@omega.webmasters.gr.jp> <41408EE1.3050402@redhat.com> <81pt4urexe.wl@omega.webmasters.gr.jp>

[GOTO Masanori]
> So I'm not surprised even it has been existed for 7 years.

Could this be the old bug reported into GNATS, libc/4348: 'Converting
charset "eucjp->sjis->iso2022jp" and "eucjp->iso2022jp" give different
result'?  If so, it has been reported a long time ago.

This is one of the locale bugs I intened to check out, but was unable
to look into when the GNATS database was removed.

References:
- Re: [PATCH] Remove 0x005C conversion from __jisx0208_from_ucs4_lat1 for ISO-2022-JP
  - From: GOTO Masanori
- Re: [PATCH] Remove 0x005C conversion from __jisx0208_from_ucs4_lat1for ISO-2022-JP
  - From: Ulrich Drepper
- Re: [PATCH] Remove 0x005C conversion from __jisx0208_from_ucs4_lat1 for ISO-2022-JP
  - From: GOTO Masanori

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]