From: "Stefan Monnier" <monnier+gnu/emacs@RUM.cs.yale.edu>
Cc: Jason Rumney <jasonr@gnu.org>, Richard Stallman <rms@gnu.org>,
monnier+gnu/emacs@rum.cs.yale.edu, emacs-devel@gnu.org
Subject: Re: Unify on encoding
Date: Wed, 20 Mar 2002 07:23:45 -0500 [thread overview]
Message-ID: <200203201223.g2KCNjP11154@rum.cs.yale.edu> (raw)
In-Reply-To: Pine.SUN.3.91.1020320075422.25160B@is
>
> On 19 Mar 2002, Jason Rumney wrote:
>
> > The escape route would be to select an iso2022 or emacs-mule coding
> > system from the expanded list offered. Or do those get unified as well?
>
> I don't know; I didn't yet have time to try this mode. Perhaps Stefan
> can answer that.
>
> In general, iso-2022 tags each charset with a special escape sequence, so
> at least in principle, you could have, say, latin-2 characters retagged
> as latin-1 there. But I don't know if that actually happens.
No, as I said, any char that can be encoded by a coding-system will be
encoded just as it was before. The only difference is now some coding
systems can encode more chars than before.
Stefan
_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/emacs-devel
next prev parent reply other threads:[~2002-03-20 12:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-17 22:28 Unify on encoding Stefan Monnier
2002-03-18 6:29 ` Eli Zaretskii
2002-03-18 14:33 ` Stefan Monnier
2002-03-18 16:10 ` Eli Zaretskii
2002-03-19 8:44 ` Richard Stallman
2002-03-19 11:17 ` Eli Zaretskii
2002-03-19 19:19 ` Jason Rumney
2002-03-19 21:12 ` Stefan Monnier
2002-03-20 5:56 ` Eli Zaretskii
2002-03-20 12:23 ` Stefan Monnier [this message]
2002-03-18 20:06 ` Richard Stallman
-- strict thread matches above, loose matches on Subject: below --
2002-03-20 2:49 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=200203201223.g2KCNjP11154@rum.cs.yale.edu \
--to=monnier+gnu/emacs@rum.cs.yale.edu \
--cc=emacs-devel@gnu.org \
--cc=jasonr@gnu.org \
--cc=rms@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).