Gnus development mailing list
 help / color / mirror / Atom feed
From: Oliver Scholz <alkibiades@gmx.de>
Subject: Re: Gnus: UTF-8 and compatibility with other MUAs
Date: Fri, 15 Aug 2003 15:50:17 +0200	[thread overview]
Message-ID: <ubruruj1i.fsf@ID-87814.user.dfncis.de> (raw)
In-Reply-To: <m3oeyrkfnc.fsf@defun.localdomain>

Jesper Harder <harder@myrealbox.com> writes:
[...]
> To use UTF-8 by default would also be against RFC 2046:
>
> ,----[ RFC 2046, Section 4.1.2. ]
> |
> |    In general, composition software should always use the "lowest common
> |    denominator" character set possible.  For example, if a body contains
> |    only US-ASCII characters, it SHOULD be marked as being in the US-
> |    ASCII character set, not ISO-8859-1, which, like all the ISO-8859
> |    family of character sets, is a superset of US-ASCII.  More generally,
> |    if a widely-used character set is a subset of another character set,
> |    and a body contains only characters in the widely-used subset, it
> |    should be labelled as being in that subset.  This will increase the
> |    chances that the recipient will be able to view the resulting entity
> |    correctly.
> `----
[...]

That's not how I read the section you quoted. In my reading this
means that you should not declare the message to be in UTF-8, when it
contains only ASCII characters. For characters from the right hand
part of ISO 8859-1 this is not so simple: Latin-1 (as a coded
character set) may be a subset of UCS. But Latin-1 (as a character
encoding scheme) is _not_ a subset of UTF-8.

The lowest common denominator for most German text is ISO 646-DE. For
most Danish text (I presume) ISO 646-DK. Virtually nobody uses those
coding systems anymore, and IMNSHO nobody should use them. (I have
implemented ISO 646-DE for GNU Emacs in a way that it could be easily
extended to other national variants of ISO 646, in case you are
interested ...)

Sure, one could say that the national variants of ISO 646 are excluded
by the phrase “widely-used character sets”, but that is a bit too
fuzzy for my taste. Taken literally nobody should use ISO 8859-15
then, unless the message really contains an € (or one of the other 7
characters). Maybe this is what this section wants to say, but then I
dare say that it doesn't make much sense as a technical rule and I am
glad that it is not stated in a way that makes it mandatory.

    Oliver
-- 
28 Thermidor an 211 de la Révolution
Liberté, Egalité, Fraternité!




  reply	other threads:[~2003-08-15 13:50 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 [this message]
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
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=ubruruj1i.fsf@ID-87814.user.dfncis.de \
    --to=alkibiades@gmx.de \
    /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).