From: Simon Josefsson <jas@extundo.com>
Cc: ding@gnus.org
Subject: Re: charset=macintosh
Date: Sat, 08 Mar 2003 16:55:49 +0100 [thread overview]
Message-ID: <iluptp1j1iy.fsf@latte.josefsson.org> (raw)
In-Reply-To: <86k7f9g8sb.fsf@ieee.org> (Jorge Godoy's message of "Sat, 08 Mar 2003 12:47:16 -0300")
Jorge Godoy <godoy@metalab.unc.edu> writes:
> 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.
>>
>> Do you have a better guess?
>
> Isn't it obligatory to fill in the charset at message headers?
> Instead of guessing, Gnus should --- I think it already does --- use
> this information to choose the charset.
Yes, and Gnus does this. I think the thread is about when this
information isn't available, which in some communities can be a large
proportion.
> If nothing is filled, them use the locale the use is in and add a
> notice that the message has an obligatory information missing.
Gnus should be more helpful, and already is since it allows certain
hierarchies to use other charsets (see `gnus-group-charset-alist').
For articles without MIME tags, in groups not in g-g-c-a, it would be
nice if Gnus could guess better -- like trying to UTF-8 decode it,
which typically only fails when data wasn't UTF-8 encoded, and then go
on and try other encodings. Emacs' decoding functions behave a little
strange, but onces fixed Gnus should be able to do this.
next prev parent reply other threads:[~2003-03-08 15:55 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 ` Simon Josefsson [this message]
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 ` charset=macintosh Jesper Harder
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=iluptp1j1iy.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).