From: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: emacs-devel@gnu.org, mew-int@mew.org
Subject: [mew-int 01590] Re: windows 1252
Date: 04 Nov 2003 10:13:35 -0500 [thread overview]
Message-ID: <jwvy8uwf9ww.fsf-monnier+emacs/devel@vor.iro.umontreal.ca> (raw)
In-Reply-To: <20031104.111334.60445673.kazu@iijlab.net>
> (1) Backgourd compatibility to non-Mule Emacsen.
> Non-Mule Emacsen use 8bit as ISO-8859-1. Thus, to share the
> cache among Mule Emacsen and non-Mule Emacsen, we need to
> character set whose 8bit is ISO-8859-1.
utf-8 would be ideal here.
> (2) Co-exist of Emacs and XEmacs.
> The 'emacs-mule coding-system is not appropriate since XEmacs
> has a different internal representation from Emacs'one. Note
> Emacsen use different 'emacs-mule coding-system among
> versions.
iso-2022 would be the answer here.
> The one-and-only coding-system which, I found, meets the requirements
> above is 'ctext.
It's unfortunate, but I guess it makes sense.
It should be possible to make ctext-with-extensions work for your case.
BTW, windows-1252 should internally be turned into a mix of chars from
various charsets and they should (hopefully) all be encodable directly in
ctext, so I'm not sure what is your exact problem. Could you describe what
currently happens with windows-1252 and what you'd like to see instead ?
Stefan
next prev parent reply other threads:[~2003-11-04 15:13 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20031029.160819.120233945.kazu@iijlab.net>
[not found] ` <20031029.082403.193886873.wl@gnu.org>
[not found] ` <20031030.175736.39971315.kazu@iijlab.net>
2003-10-30 14:41 ` [mew-int 01581] Re: windows 1252 Werner LEMBERG
2003-10-31 11:04 ` [mew-int 01579] " Kenichi Handa
2003-10-31 12:39 ` [mew-int 01583] " Kazu Yamamoto
2003-11-01 15:36 ` [mew-int 01584] " Eli Zaretskii
2003-11-02 6:41 ` [mew-int 01582] " Stephen J. Turnbull
2003-11-04 2:13 ` [mew-int 01586] " Kazu Yamamoto
2003-11-04 5:55 ` [mew-int 01585] " Eli Zaretskii
2003-11-04 6:13 ` [mew-int 01587] " Kazu Yamamoto
2003-11-04 6:23 ` [mew-int 01589] " Stephen J. Turnbull
2003-11-04 15:13 ` Stefan Monnier [this message]
2003-11-04 15:55 ` [mew-int 01591] " Kazu Yamamoto
2003-11-04 17:04 ` [mew-int 01590] " Stefan Monnier
2003-11-04 18:45 ` Stephen J. Turnbull
2003-11-05 1:59 ` [mew-int 01594] " Kazu Yamamoto
2003-11-05 5:00 ` [mew-int 01593] " Stephen J. Turnbull
2003-11-07 7:30 ` Kenichi Handa
2003-11-07 7:28 ` [mew-int 01597] " Kenichi Handa
2003-11-07 8:21 ` [mew-int 01599] " Kazu Yamamoto
2003-11-07 7:13 ` [mew-int 01596] " Kenichi Handa
2003-11-10 7:11 ` [mew-int 01607] " Kazu Yamamoto
2003-11-10 7:42 ` [mew-int 01608] " Kenichi Handa
2003-11-12 16:36 ` [mew-int 01596] " Stephen J. Turnbull
2003-11-13 1:01 ` Kenichi Handa
2003-11-13 16:32 ` Stephen J. Turnbull
2003-11-14 2:57 ` Kenichi Handa
2003-11-14 11:20 ` Stephen J. Turnbull
2003-11-14 12:02 ` Kenichi Handa
2003-11-13 19:49 ` Eli Zaretskii
2003-11-14 3:39 ` [mew-int 01621] " Kenichi Handa
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=jwvy8uwf9ww.fsf-monnier+emacs/devel@vor.iro.umontreal.ca \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=mew-int@mew.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).