From: Eli Zaretskii <eliz@gnu.org>
To: Andreas Schwab <schwab@suse.de>
Cc: 66760@debbugs.gnu.org, yuruijie@sics.ac.cn
Subject: bug#66760: 29.1; [BUG] GB18030 Incorrect Encoding
Date: Sat, 04 Nov 2023 10:25:07 +0200 [thread overview]
Message-ID: <83h6m253j0.fsf@gnu.org> (raw)
In-Reply-To: <mvmwmv979dg.fsf@suse.de> (message from Andreas Schwab on Thu, 26 Oct 2023 16:20:59 +0200)
> Cc: 66760@debbugs.gnu.org
> From: Andreas Schwab <schwab@suse.de>
> Date: Thu, 26 Oct 2023 16:20:59 +0200
>
> On Okt 26 2023, Ruijie Yu wrote:
>
> > I have noticed that in GB18030 encoding, certain ranges of characters
> > have incorrect encodings.
> >
> > One example is U+217A (SMALL ROMAN NUMERAL ELEVEN). The expected
> > encoding is 81 36 C5 30 (as can be seen from the GB18030 standard [1]
> > and verified from other programs such as iconv and MySQL), whereas the
> > observed encoding within Emacs is 81 36 C4 39, with a 1-codepoint
> > offset.
>
> This is a bug in the generation of GB180304.map. The gb180303.awk
> script assumes that the 4-byte encodings of GB18030 are filling the
> holes in sequence of characters with a 2-byte encoding by Unicode
> codepoint order, but there are some places where codepoints from the PUA
> area are inserted into the sequence. For example, U+1E3E maps to 81 35
> F4 36, the next codepoint not mapped to a 2-byte code is U+1E40, but
> that maps to 81 35 F4 38, whereas 81 35 F4 37 is the encoding of U+E7C7.
> So the output gets out of sync.
Thanks. I don't think I understand the issue well enough, so patches
are welcome to fix this problem in the Awk script.
prev parent reply other threads:[~2023-11-04 8:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-26 11:43 bug#66760: 29.1; [BUG] GB18030 Incorrect Encoding Ruijie Yu
2023-10-26 13:26 ` Eli Zaretskii
2023-10-26 14:20 ` Andreas Schwab
2023-11-04 8:25 ` Eli Zaretskii [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83h6m253j0.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=66760@debbugs.gnu.org \
--cc=schwab@suse.de \
--cc=yuruijie@sics.ac.cn \
/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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).