From: "Kazu Yamamoto" <kazu@iijlab.net>
Subject: Re: [mew-int 00737] Re: (no subject)
Date: Mon, 25 Feb 2002 10:11:29 +0900 (JST) [thread overview]
Message-ID: <20020225.101129.117063194.kazu@iijlab.net> (raw)
In-Reply-To: <20020223.151106.01367146.Takaaki.Ota@am.sony.com>
From: Tak Ota <Takaaki.Ota@am.sony.com>
Subject: [mew-int 00737] Re: (no subject)
> Therefore many buffers in Mew sets ctext-unix as the default coding
> system. However, I have no idea how this decision was made.
Yes, this is intentional.
Ctext is only character set which can conver ISO-2022 related
character sets and ISO-8859-1.
If we use US-ASCII and 8bit portion of ctext, this is identical to
ISO-8859-1. This is friendly to non-mule EMacs, Emacs --unibyte for
example.
Of course, Emacs (--multibyte) can read ctext.
So, to my best knowledge, ctext is only the character set which can
survive in the old Emacs world and the multilingual Emacs world.
Since Mew uses the CR character as a separator in Summary mode (for
historical reasons:: selective-display was used), ctext-unix is
necessary. (CR MUST not be converted to LF).
What I can say is as follows:
(1) Since selective-display is not used anymore, another separator
rather than CR can be used. ctext will be sufficient.
(2) Even if we continue to use CR, ctext-unix is necessary only for
Summary mode. ctext is enough for other buffers.
--Kazu
_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/emacs-devel
next prev parent reply other threads:[~2002-02-25 1:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-23 6:53 ctext-pre-write-conversion barfs Tak Ota
2002-02-23 8:48 ` Eli Zaretskii
2002-02-23 16:11 ` Tak Ota
2002-02-23 18:51 ` (no subject) Eli Zaretskii
2002-02-23 23:11 ` Tak Ota
2002-02-25 1:11 ` Kazu Yamamoto [this message]
2002-02-25 6:55 ` [mew-int 00737] " Eli Zaretskii
2002-02-26 16:51 ` ctext-pre-write-conversion barfs Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2002-02-25 7:10 [mew-int 00737] Re: (no subject) Kenichi Handa
2002-02-26 16:52 ` 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=20020225.101129.117063194.kazu@iijlab.net \
--to=kazu@iijlab.net \
/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).