GNU bug report logs - #11073
24.0.94; BIDI-related crash in redisplay with certain byte sequences

Previous Next

Full log

Message #29 received at 11073 <at> debbugs.gnu.org (full text, mbox):

From: Kenichi Handa <handa <at> m17n.org>
To: Stefan Monnier <monnier <at> iro.umontreal.ca>
Cc: eliz <at> gnu.org, 11073 <at> debbugs.gnu.org
Subject: Re: bug#11073: 24.0.94;
	BIDI-related crash in redisplay with certain byte sequences
Date: Thu, 29 Mar 2012 14:19:50 +0900

In article <jwviphrft9z.fsf-monnier+INBOX <at> gnu.org>, Stefan Monnier <monnier <at> iro.umontreal.ca> writes:

> I understand this part.  The part I don't understand is why we do
> unification when reading a char from the buffer's text.  That is: why
> unify chars in `int' (or Lisp_Object) form but not in the
> internal-utf-8 representation?

> I would expect the unification to happen during encoding/decoding

Usually, yes.  But as far as there is a code space in high
area for a CJK charset, it is unavoidable to have a
buffer/string that contains a character represented by a
byte sequence in that high area as the test case of
Bug#11073.  And, as "unification" means to treat such a
character the same way as the unified character, I thought
they both have the same character code.

---
Kenichi Handa
handa <at> m17n.org

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.