From: Kenichi Handa <handa@m17n.org>
Cc: reinersteib+gmane@imap.cc, emacs-devel@gnu.org
Subject: Re: [reinersteib+gmane@imap.cc: Display of gb2312 in `emacs -nw']
Date: Tue, 30 Nov 2004 17:26:22 +0900 (JST) [thread overview]
Message-ID: <200411300826.RAA01928@etlken.m17n.org> (raw)
In-Reply-To: <E1CY7fK-0005LW-P9@fencepost.gnu.org> (message from Richard Stallman on Sat, 27 Nov 2004 13:51:26 -0500)
In article <E1CY7fK-0005LW-P9@fencepost.gnu.org>, Richard Stallman <rms@gnu.org> writes:
> I'll check if we can run
> pre-write-conversion safely at that time. Please wait for a
> while.
> Please respond to this message when you've had a chance to think about
> it and decide what to do.
Richard Stallman <rms@gnu.org> writes:
> In general, running Lisp code from redisplay is safe nowadays.
> I looked at the callers of write_glyphs, and it seems to be safe
> to run Lisp code there. I am not quite certain it is ok
> to get an error from there, but it looks safe.
Ok, I've just committed appropriate changes. As
pre-write-conversion is called via safe_call, I think an
error in that function won't propagate to the main code.
Reiner Steib <reinersteib+gmane@imap.cc> writes:
> To reproduce:
> Save the following to a file `gb2312.txt' and start emacs in an UTF-8
> enabled xterm:
> uxterm -font '-misc-fixed-medium-r-normal--14-*-*-*-*-*-iso10646-1' \
> -e emacs -nw -Q gb2312.txt
As I don't have a proper font to be used with uxterm, I
tested the new code with mlterm under LANG=ja_JP.UTF-8 and
confirmed that all subst-XXX.el are automatically loaded,
and thus encoding to utf-8 is done correctly.
Please try the latest CVS code.
As the change to term.c is rather big, it is better that
people test the the new code with -nw on various terminals
and encodings. I think the new code is much faster unless
the encoding requires pre-write-conversion.
---
Ken'ichi HANDA
handa@m17n.org
next parent reply other threads:[~2004-11-30 8:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1CWmsr-0001th-8Q@fencepost.gnu.org>
[not found] ` <200411261200.VAA22834@etlken.m17n.org>
[not found] ` <E1CY7fK-0005LW-P9@fencepost.gnu.org>
2004-11-30 8:26 ` Kenichi Handa [this message]
2004-11-30 14:20 ` [reinersteib+gmane@imap.cc: Display of gb2312 in `emacs -nw'] Reiner Steib
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=200411300826.RAA01928@etlken.m17n.org \
--to=handa@m17n.org \
--cc=emacs-devel@gnu.org \
--cc=reinersteib+gmane@imap.cc \
/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).