From: Kenichi Handa <handa@m17n.org>
Cc: emacs-devel@gnu.org
Subject: Re: display table for eight-bit-graphic
Date: Tue, 18 Mar 2003 16:26:18 +0900 (JST) [thread overview]
Message-ID: <200303180726.QAA28116@etlken.m17n.org> (raw)
In-Reply-To: <E18pvAD-0004ru-00@fencepost.gnu.org> (message from Richard Stallman on Mon, 03 Mar 2003 13:59:49 -0500)
Sorry for the late reply on this matter.
In article <E18pvAD-0004ru-00@fencepost.gnu.org>, Richard Stallman <rms@gnu.org> writes:
>> It is definitely intended to use the display table for multibyte
>> buffers--but I think that's not actually the issue you are talking
>> about.
> I'm talking that using the display table in multibyte
> session is not good.
>> Anyway, I don't think this actually contradicts anything I said.
>> The display table is used for unibyte buffers, too. If we
>> want unibyte buffers to display the international graphics,
>> we have to set up the display table for codes 128-255.
> We don't have to use the display table even for unibyte
> buffers. Even for a unibyte buffer,
> get_next_display_element in xdisp.c doesn't generate a octal
> form "\XXX" for a code in the range 128-255 if the code can
> be converted to a multibyte character by
> unibyte_char_to_multibyte.
> It sounds like you're suggesting that we eliminate the display
> table feature.
No. The display table is useful even in a multibyte buffer
if Emacs is running on a terminal like the case of MSDOS.
For instance, if one is using a terminal that can display
only ASCII, he may want to setup the display table so that,
for instance, `À' (A-grave) is displayed as "A`".
> Perhaps the display table is obsolete as a means of displaying
> non-ASCII characters, assuming we set up for proper conversion
> to unibyte according to the language in use.
I think the display table is obsolete only as a means of
displaying 8-bit characaters in unibyte buffer and
eight-bit-control/graphic characters. At least in the
latter case, they should be displayed by octal-form by
default.
---
Ken'ichi HANDA
handa@m17n.org
next prev parent reply other threads:[~2003-03-18 7:26 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <rzqbs263bxm.fsf@albion.dl.ac.uk>
2003-01-25 1:16 ` display table for eight-bit-graphic Kenichi Handa
2003-01-25 10:17 ` Kai Großjohann
2003-01-25 22:24 ` Ehud Karni
2003-01-26 14:27 ` Kai Großjohann
2003-01-26 15:37 ` Richard Stallman
2003-01-27 2:20 ` Kenichi Handa
2003-01-29 0:04 ` Richard Stallman
2003-01-29 11:03 ` Kenichi Handa
2003-03-03 18:59 ` Richard Stallman
2003-03-03 20:41 ` Eli Zaretskii
2003-03-18 7:26 ` Kenichi Handa [this message]
2003-03-19 8:48 ` Richard Stallman
2003-03-19 10:58 ` Kenichi Handa
2003-03-21 19:07 ` Richard Stallman
2003-02-03 14:28 ` Dave Love
2003-02-03 14:29 ` Dave Love
2003-02-03 14:32 ` 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
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=200303180726.QAA28116@etlken.m17n.org \
--to=handa@m17n.org \
--cc=emacs-devel@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).