public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "glibcbugz at ghalkes dot nl" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug libc/12830] New: ISO-2022-JP-2 maps C1 control characters incorrectly Date: Wed, 01 Jun 2011 07:42:00 -0000 [thread overview] Message-ID: <bug-12830-131@http.sourceware.org/bugzilla/> (raw) http://sourceware.org/bugzilla/show_bug.cgi?id=12830 Summary: ISO-2022-JP-2 maps C1 control characters incorrectly Product: glibc Version: 2.13 Status: NEW Severity: normal Priority: P2 Component: libc AssignedTo: drepper.fsp@gmail.com ReportedBy: glibcbugz@ghalkes.nl In the ISO-2022-JP-2 converter, the C1 control codes (U0080-U009F) are encoded as 1B 2E 41 1B 4E [00 - 1F] (i.e., load ISO-8859-1 in the G2 graphics set, use single shift to set G2 and encode the byte [00 - 1F]). However, if I understand the standard correctly, switching to the G2 set _only_ changes the mapping of the 96 characters in the range 20-7F (or the 94 charaacters in the range 21-7E if a smaller set is used). The control characters are unaffected. To access the C1 control set, one should use 1B [40 - 5F]. This is actually done for the encoding of the "single shift 2" control (U+008E) in the sequence above, which is encoded as 1B 4E. -- Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
next reply other threads:[~2011-06-01 7:42 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-06-01 7:42 glibcbugz at ghalkes dot nl [this message] 2011-09-09 19:50 ` [Bug libc/12830] " drepper.fsp at gmail dot com 2011-09-20 13:21 ` glibcbugz at ghalkes dot nl 2012-01-04 20:03 ` aj at suse dot de 2012-12-19 10:51 ` schwab@linux-m68k.org 2014-02-07 2:56 ` [Bug localedata/12830] " jsm28 at gcc dot gnu.org 2014-06-27 13:14 ` fweimer at redhat dot com
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-12830-131@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sources.redhat.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).