From: Kenichi Handa <handa@m17n.org>
Cc: emacs-devel@gnu.org
Subject: Re: \225 and so on
Date: Tue, 8 Apr 2003 20:39:31 +0900 (JST) [thread overview]
Message-ID: <200304081139.UAA14496@etlken.m17n.org> (raw)
In-Reply-To: <200304080447.NAA14014@etlken.m17n.org> (message from Kenichi Handa on Tue, 8 Apr 2003 13:47:18 +0900 (JST))
In article <200304080447.NAA14014@etlken.m17n.org>, Kenichi Handa <handa@m17n.org> writes:
> Currently, \222, \223, \224 are registered in
> latin-extra-code-table. We can add \225 to it. And, by
> paying attention to latin-extra-code-table in
> find-coding-systems-region-internal, we can make Emacs to
> work as you wish. I'll work on it soon.
I've just installed it. Now iso-latin-1 can read/write a
file that contains \225.
> In article <E192ist-0000pD-00@fencepost.gnu.org>, Richard Stallman <rms@gnu.org> writes:
>> It should be treated as Latin-1, or perhaps as Latin-whatever based on
>> one's usual coding system preferences.
Currently, only iso-latin-1/8/9 has t for
accept-latin-extra-code flag. So, only they can read/write
such a file. I don't know why iso-latin-2/3/4/5 doesn't.
Perhaps, those who uses those coding systems won't encounter
such bytes (\222..\225) that much and they prefer reading
such a file in raw-text. I'm not sure. At least, I don't
rember any complaints about the current definition of those
coding systems.
---
Ken'ichi HANDA
handa@m17n.org
next prev parent reply other threads:[~2003-04-08 11:39 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-04 22:24 \225 and so on Richard Stallman
2003-04-07 15:37 ` Andreas Schwab
2003-04-08 2:30 ` Richard Stallman
2003-04-08 4:47 ` Kenichi Handa
2003-04-08 11:39 ` Kenichi Handa [this message]
2003-04-09 1:59 ` Richard Stallman
2003-04-09 5:32 ` Eli Zaretskii
2003-04-09 2:00 ` Richard Stallman
2003-04-09 2:40 ` Kenichi Handa
2003-04-09 10:18 ` Alex Schroeder
2003-04-09 11:05 ` Kenichi Handa
2003-04-10 6:22 ` Richard Stallman
2003-04-07 16:51 ` Benjamin Riefenstahl
2003-04-08 2:31 ` Richard Stallman
2003-04-08 4:16 ` Eli Zaretskii
2003-04-08 13:07 ` Benjamin Riefenstahl
2003-04-09 5:33 ` Eli Zaretskii
2003-04-08 4:13 ` Eli Zaretskii
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=200304081139.UAA14496@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).