From: Kenichi Handa <handa@m17n.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 11073@debbugs.gnu.org
Subject: bug#11073: 24.0.94; BIDI-related crash in redisplay with certain byte sequences
Date: Fri, 06 Apr 2012 10:13:12 +0900 [thread overview]
Message-ID: <tl7pqblzmqf.fsf@m17n.org> (raw)
In-Reply-To: <jwvd37os3k5.fsf-monnier+INBOX@gnu.org> (message from Stefan Monnier on Tue, 03 Apr 2012 21:17:16 -0400)
In article <jwvd37os3k5.fsf-monnier+INBOX@gnu.org>, Stefan Monnier <monnier@iro.umontreal.ca> writes:
>>> But isn't this (unify-charset 'big5 "MyBig5.map") performed in the .emacs?
> > Usually yes. But, in that case, if .emacs is encoded in
> > Big5 and it contains some Big5 PUA chars, they are not
> > unified while loading .emacs.
> Hmm... that doesn't sound like it would be a very common problem, but
> it's not completely hypothetical either. Would this problem also come
> up in a BIG5 locale? If not, then I think we can ignore this problem.
If it ever comes up, it is mostly for people in BIG5 locale.
But, please note that the reason I used BIG5 as an example
is just because that charset name is short. Almost all CJK
charsets have PUA (officially or just by convention).
>>> Is it really important to support adding unification rules
>>> after decoding took place? If so, why?
> > As I wrote, I can't tell how important it is. It may be very
> > important for those (but I guess very few) who need the above
> > operation, but not important for the majority.
> > I'm ok to remove such a feature if the maintainers decide that.
> The problem with it is that it costs all the time for everyone, and it
I believe the extra cost is almost negligible because such
(dynamic) unification happens only for characters that is
greater than MAX_UNICODE_CHAR.
> makes the behavior of some macros subtly more complex/different and
> hence adds a nasty complexity.
That's mostly because I didn't write a proper comments on
the relavant macros, and didn't provide a better macros for
such a case as Eli's.
> So if at all possible, I'd rather find a way to remove it (not for
> 24.1, obviously).
I myself think that it doens't cause much problem even if we
keep this functionality, but, also don't raise strong
objection to remove it for 24.2.
>>> And also, what about removing unification rules after decoding?
> > When one tells Emacs to unify some chars, and then reads a file
> > containing those chars, there's no way to dis-unify them.
> But I guess this problem is even much less common.
Yes. That's why I didn't implement such a feature.
---
Kenichi Handa
handa@m17n.org
next prev parent reply other threads:[~2012-04-06 1:13 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
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 [this message]
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=tl7pqblzmqf.fsf@m17n.org \
--to=handa@m17n.org \
--cc=11073@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).