From: Jesper Harder <harder@myrealbox.com>
Subject: Re: charset=macintosh
Date: Sat, 08 Mar 2003 20:47:34 +0100 [thread overview]
Message-ID: <m3u1edwsh5.fsf@defun.localdomain> (raw)
In-Reply-To: <843clxud7u.fsf@lucy.is.informatik.uni-duisburg.de>
kai.grossjohann@uni-duisburg.de (Kai Großjohann) writes:
> Jesper Harder <harder@myrealbox.com> writes:
>
>> Just because you're using UTF-8, mac-roman, EBCDIC or whatever on
>> your local system doesn't mean that it's a good guess that you'll
>> receive mail and news using this charset.
>
> I think this guess is better than no guess at all.
Well, I think experience shows that UTF-8 isn't a good guess. It's a
bad guess for dk.*, and as Karl says also for de.*.
Previously `gnus-group-charset-alist' had (".*" iso-8859-1) as the last
entry -- this was probably better for the majority of users.
I haven't got any statistics to back it up, but I suspect that clients
which send UTF-8 are probably newer, and thus more likely to include a
proper MIME charset declaration.
So, I think it's much more likely that the charset of a message with an
undeclared charset is iso-8859-x rather than UTF-8.
next prev parent reply other threads:[~2003-03-08 19:47 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-07 17:39 charset=macintosh Karl Eichwalder
2003-03-07 18:25 ` charset=macintosh Simon Josefsson
2003-03-07 19:30 ` charset=macintosh Karl Eichwalder
2003-03-07 19:45 ` charset=macintosh Jesper Harder
2003-03-07 20:40 ` charset=macintosh Karl Eichwalder
2003-03-07 23:05 ` charset=macintosh Jesper Harder
2003-03-08 14:47 ` charset=macintosh Kai Großjohann
2003-03-08 15:47 ` charset=macintosh Jorge Godoy
2003-03-08 15:55 ` charset=macintosh Simon Josefsson
2003-03-08 19:52 ` charset=macintosh Jesper Harder
2003-03-08 20:09 ` charset=macintosh Simon Josefsson
2003-03-08 16:00 ` charset=macintosh Kai Großjohann
2003-03-08 16:47 ` charset=macintosh Frank Schmitt
2003-03-08 19:44 ` charset=macintosh Simon Josefsson
2003-03-08 19:47 ` Jesper Harder [this message]
2003-03-08 20:17 ` charset=macintosh Simon Josefsson
2003-03-09 3:56 ` charset=macintosh Jesper Harder
2003-03-09 11:48 ` charset=macintosh Simon Josefsson
2003-03-14 23:02 ` charset=macintosh Jesper Harder
2003-03-07 19:47 ` charset=macintosh Simon Josefsson
2003-03-07 21:02 ` charset=macintosh Karl Eichwalder
2003-03-07 21:24 ` charset=macintosh Simon Josefsson
2003-04-01 17:51 ` mm-coding-system-priorities (was: charset=macintosh) Reiner Steib
2003-04-12 19:53 ` mm-coding-system-priorities Lars Magne Ingebrigtsen
2003-04-13 20:44 ` mm-coding-system-priorities Reiner Steib
2003-04-15 21:54 ` mm-coding-system-priorities Lars Magne Ingebrigtsen
2003-03-08 2:39 ` TeX input method? (Was: charset=macintosh) Jinhyok Heo
2003-03-08 6:33 ` TeX input method? Karl Eichwalder
2003-03-09 17:07 charset=macintosh Jesper Harder
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=m3u1edwsh5.fsf@defun.localdomain \
--to=harder@myrealbox.com \
/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).