From: Simon Josefsson <jas@extundo.com>
Cc: ding <ding@gnus.org>
Subject: Re: Gnus: UTF-8 and compatibility with other MUAs
Date: Fri, 15 Aug 2003 01:05:04 +0200 [thread overview]
Message-ID: <iluptj7g7rz.fsf@latte.josefsson.org> (raw)
In-Reply-To: <plop87brus6y07.fsf@gnu-rox.org> (Xavier Maillard's message of "Thu, 14 Aug 2003 17:48:40 +0200")
Xavier Maillard <zedek@gnu-rox.org> writes:
> Hi,
>
> I know Emacs is able to use utf-8 encoding so Gnus is.
>
> My question is more a question of compliance with other MUAs.
> Would you recommend your users to use utf-8 as a default encoding
> system ? AFAIK, I can't see many MUAs aware of it and worst almost
> nobody is using utf-8 which was presented as the future. So what is the
> problem with utf in general that prevent users in general to use it
> defaultly ?
IMHO:
Users should use the oldest charset widely deployed, or preferred, in
their own geographic region that is able to encode what they write.
This means if a user write only ASCII, it is tagged as ASCII (or
rather not tagged at all).
And if a (northern?) European user write å it should use iso-8859-1.
And if a european user write Ελληνικά it should use iso-8859-7.
And if a european user write € it should use iso-8859-15. (One could
argue that iso-8859-15 is too recent and that it may make sense to go
directly to UTF-8, but my experience, as a northern european user, is
that iso-8859-15 is more appropriate, since the almost-compatibility
with iso-8859-1 is friendlier for people with old software.)
And if a european user write € and ά it should use UTF-8. (I'm
assuming no 8859-* can encode both € and ά.)
This also means that it is wrong to use JP-2022-2, for european users,
even though it technically may be able to encode some strings, that
contain characters from 8859-* that isn't available in any single
8859-*. Instead they should go to UTF-8.
I think this is how Gnus works though, unless you are in a UTF-8
locale and uses an old Emacs (then I think it will skip the 8859-*
step, but I might be wrong).
This logic might be flawed if the receiver is in another geographic
region, of if a user mostly communicate internationally. Still, I'd
probably use the above logic even if I sent something to a Japanese
user, and expect them to use JP-2022-2 (or whatever) in return.
Perhaps some day we can try ASCII first, then fall back to UTF-8. But
that will take a long time. Even moving to ISO-8859-1 in northern
Europe took a long time, and still isn't finished. I still use IBMPC2
(CP437?) in some regional communication channels.
next prev parent reply other threads:[~2003-08-14 23:05 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-14 15:48 Xavier Maillard
2003-08-14 22:39 ` Frank Schmitt
2003-08-15 18:22 ` Xavier Maillard
2003-08-14 23:01 ` Jesper Harder
2003-08-15 13:50 ` Oliver Scholz
2003-08-15 16:48 ` Jesper Harder
2003-08-15 18:10 ` Oliver Scholz
2003-08-16 0:23 ` Jesper Harder
2003-08-16 9:48 ` Oliver Scholz
2003-08-16 13:01 ` Jesper Harder
2003-08-16 15:36 ` Oliver Scholz
2003-08-16 17:14 ` Reiner Steib
2003-08-16 19:29 ` Oliver Scholz
2003-08-19 14:54 ` Miles Bader
2003-08-20 15:24 ` Reiner Steib
2003-08-21 0:20 ` Miles Bader
2003-08-16 17:23 ` Simon Josefsson
2003-08-16 19:18 ` Oliver Scholz
2003-08-16 22:24 ` Simon Josefsson
2003-08-17 12:30 ` Benjamin Riefenstahl
2003-08-17 16:40 ` Oliver Scholz
2003-08-18 2:20 ` James H. Cloos Jr.
2003-08-18 15:58 ` Benjamin Riefenstahl
2003-08-18 2:16 ` James H. Cloos Jr.
2003-08-18 2:09 ` James H. Cloos Jr.
2003-08-28 13:38 ` Jens Müller
2003-08-28 13:35 ` Jens Müller
2003-08-17 0:57 ` Jesper Harder
2003-08-17 17:24 ` Oliver Scholz
2003-08-17 18:21 ` Matthias Andree
2003-08-15 18:24 ` Xavier Maillard
2003-08-16 0:35 ` Jesper Harder
2003-08-14 23:05 ` Simon Josefsson [this message]
2003-08-15 17:00 ` Oliver Scholz
2003-08-16 7:43 ` Ivan Boldyrev
2003-08-17 17:27 ` Oliver Scholz
2003-08-18 6:01 ` Steinar Bang
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=iluptj7g7rz.fsf@latte.josefsson.org \
--to=jas@extundo.com \
--cc=ding@gnus.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.
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 NNTP newsgroup(s).