From: Kenichi Handa <handa@etl.go.jp>
Cc: bug-gnu-emacs@gnu.org
Subject: Re: correcting Emacs CHAR_COMPONENTS_VALID_P
Date: Thu, 18 Apr 2002 11:25:46 +0900 (JST) [thread overview]
Message-ID: <200204180225.LAA07395@etlken.m17n.org> (raw)
In-Reply-To: message from Dave Love on 16 Apr 2002 00:18:34 +0100
Dave Love <d.love@dl.ac.uk> writes:
> You wrote:
>> Dave Love <d.love@dl.ac.uk> writes:
>>
>> > I accidentally made a bogus character from a 94x94 charset like
>> > (make-char 'japanese-jisx0208 32 32)
>>
>> > and was confused by the result of inserting it.
>>
>> > Is it worth fixing, or is it intentional for efficiency or something?
>> > It isn't trivial to fix because several functions and macros are
>> > affected.
>>
>> The current behaviour is intentional. Efficiency is one
>> reason. Another reason is historical one. There exists
>> many files that contains invalid byte sequences such as 0xA0
>> 0xA0 (especially EUC-GB). Before we introduce
>> eight-bit-control and eight-bit-graphic, we couldn't decode
>> them properly if we treat them as invalid byte sequence.
>> Thus I made the rule loosen. Now, as we have
>> eight-bit-graphic, we can make the rule firm, but I think
>> it's not worth spending time on it.
> I think that deserves commentary in the sources to avoid anyone else
> wasting time looking at it.
I agree, and thank you for pointing out that. Would you
please add a proper comment to the source? I still can't
contribute any code for the current version of Emacs. :-(
---
Ken'ichi HANDA
handa@etl.go.jp
next reply other threads:[~2002-04-18 2:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-18 2:25 Kenichi Handa [this message]
[not found] <200204130410.NAA29660@etlken.m17n.org>
2002-04-15 23:18 ` correcting Emacs CHAR_COMPONENTS_VALID_P Dave Love
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200204180225.LAA07395@etlken.m17n.org \
--to=handa@etl.go.jp \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.