From: Kenichi Handa <handa@m17n.org>
Cc: bug-gnu-emacs@gnu.org, handa@m17n.org
Subject: Re: bites assumed set mid UTF-8
Date: Tue, 07 Mar 2006 13:52:33 +0900 [thread overview]
Message-ID: <E1FGUBV-00068M-00@etlken> (raw)
In-Reply-To: <87r75fignl.fsf@jidanni.org> (message from Dan Jacobson on Tue, 07 Mar 2006 02:15:10 +0800)
In article <87r75fignl.fsf@jidanni.org>, Dan Jacobson <jidanni@jidanni.org> writes:
> Bad bad bad. Emacs 21.4.1 shows the same Chinese character ("nuclear")
> even though the second bit string is not valid UTF-8. Cc'd Handa.
> 11100110 10100000 10111000
> 11100110 00100000 10111000
Thank you for the report. It is already fixed in the latest
CVS code. With it, the second byte sequence (invalid utf-8)
is decoded into "\346 \270" (i.e. 8-bit-char #xe6, SPC,
8-bit-char #xb8).
---
Kenichi Handa
handa@m17n.org
prev parent reply other threads:[~2006-03-07 4:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-06 18:15 bites assumed set mid UTF-8 Dan Jacobson
2006-03-07 4:52 ` Kenichi Handa [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=E1FGUBV-00068M-00@etlken \
--to=handa@m17n.org \
--cc=bug-gnu-emacs@gnu.org \
/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).