From: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Benjamin.Riefenstahl@epost.de, sds@gnu.org, emacs-devel@gnu.org
Subject: Re: utf-8 cut/paste
Date: 26 May 2004 16:02:59 -0400 [thread overview]
Message-ID: <jwvsmdnt0wr.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <1190-Wed26May2004201148+0300-eliz@gnu.org>
>> cp1252 could have been implemented as another charset rather than being
>> mapped to a mix of 8859-1 and unicode chars.
> If we did that, it would make the unfortunate situation, whereby there
> are multiple charsets that cover the same characters, even worse.
Isn't it exactly what happened with 8859-15 ?
I never claimed it was desirable.
> Repeat after me: "multiple character sets covering the same characters
> are BAD."
You're just saying that unicode is good.
The only point I originally tried to make is that it's better to avoid
talking about Mule charsets if possible.
Stefan
next prev parent reply other threads:[~2004-05-26 20:02 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-23 18:59 utf-8 cut/paste Sam Steingold
2004-05-24 9:52 ` Benjamin Riefenstahl
2004-05-24 16:18 ` Sam Steingold
2004-05-24 19:19 ` Benjamin Riefenstahl
2004-05-24 21:00 ` Sam Steingold
2004-05-24 23:10 ` Benjamin Riefenstahl
2004-05-25 13:06 ` Sam Steingold
2004-05-25 6:02 ` Eli Zaretskii
2004-05-25 10:03 ` Benjamin Riefenstahl
2004-05-25 12:36 ` Eli Zaretskii
2004-05-25 15:41 ` Sam Steingold
2004-05-26 4:22 ` Kenichi Handa
2004-05-28 17:45 ` Sam Steingold
2004-05-29 10:04 ` Jason Rumney
2004-05-26 4:33 ` Miles Bader
2004-05-26 18:11 ` Sam Steingold
2004-05-26 19:23 ` David Kastrup
2004-05-26 11:32 ` Eli Zaretskii
2004-05-26 13:31 ` Sam Steingold
2004-05-26 12:30 ` Benjamin Riefenstahl
2004-05-26 15:48 ` Stefan Monnier
2004-05-26 18:11 ` Eli Zaretskii
2004-05-26 20:02 ` Stefan Monnier [this message]
2004-05-27 8:10 ` 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=jwvsmdnt0wr.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=Benjamin.Riefenstahl@epost.de \
--cc=emacs-devel@gnu.org \
--cc=sds@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).