From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Kenichi Handa <handa@m17n.org>
Cc: 11073@debbugs.gnu.org
Subject: bug#11073: 24.0.94; BIDI-related crash in redisplay with certain byte sequences
Date: Mon, 26 Mar 2012 08:23:58 -0400 [thread overview]
Message-ID: <jwviphrft9z.fsf-monnier+INBOX@gnu.org> (raw)
In-Reply-To: <tl7limnls97.fsf@m17n.org> (Kenichi Handa's message of "Mon, 26 Mar 2012 16:45:56 +0900")
> So, I decided at that time to give each CJK charset unique
> code space (above #x110000) in Emacs, and allow users to
> freely unify/disunify them to Unicode code space (below
> #x110000) by giving the function unify-charset.
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
only, and not during internal conversions from byte byte-sequence to int.
Stefan
next prev parent reply other threads:[~2012-03-26 12:23 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-23 10:55 bug#11073: 24.0.94; BIDI-related crash in redisplay with certain byte sequences Eli Zaretskii
2012-03-23 12:35 ` Eli Zaretskii
2012-03-23 14:27 ` Stefan Monnier
2012-03-23 15:58 ` Eli Zaretskii
2012-03-23 17:34 ` Stefan Monnier
2012-03-23 18:46 ` Eli Zaretskii
2012-03-26 7:45 ` Kenichi Handa
2012-03-26 12:23 ` Stefan Monnier [this message]
2012-03-29 5:19 ` Kenichi Handa
2012-03-29 16:04 ` Stefan Monnier
2012-04-03 2:22 ` Kenichi Handa
2012-04-03 4:22 ` Stefan Monnier
2012-04-03 5:55 ` Kenichi Handa
2012-04-03 13:02 ` Stefan Monnier
2012-04-04 0:07 ` Kenichi Handa
2012-04-04 1:17 ` Stefan Monnier
2012-04-06 1:13 ` Kenichi Handa
2012-04-06 13:13 ` Eli Zaretskii
2012-04-09 4:14 ` Kenichi Handa
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=jwviphrft9z.fsf-monnier+INBOX@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=11073@debbugs.gnu.org \
--cc=handa@m17n.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).