From: Simon Josefsson <jas@extundo.com>
Subject: Re: charset=macintosh
Date: Sat, 08 Mar 2003 21:09:22 +0100 [thread overview]
Message-ID: <iluk7f9ipsd.fsf@latte.josefsson.org> (raw)
In-Reply-To: <m3r89hws9g.fsf@defun.localdomain> (Jesper Harder's message of "Sat, 08 Mar 2003 20:52:11 +0100")
Jesper Harder <harder@myrealbox.com> writes:
> Simon Josefsson <jas@extundo.com> writes:
>
>> 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.
>
> Currently they're not good enough, IMHO. Here's an example:
>
> (detect-coding-string (encode-coding-string "dk.test.utf8-æøå" 'utf-8))
>
> => (iso-latin-1 iso-latin-1 raw-text japanese-shift-jis
> chinese-big5 no-conversion mule-utf-8)
>
> The correct answer is last in the list.
Doesn't that function use the preference order configured by the user?
For me, who runs emacs in a UTF-8 locale, it returns mule-utf-8 first.
Released emacs versions have incomplete UTF-8 support (see PROBLEMS)
and UTF-8 have a very low priority so any potential bug aren't
triggered unless they, err, really must be triggered. This is
reasonable, I think.
I've asked on emacs-devel that emacs in CVS (both 21.3 and HEAD),
which supposedly has complete Unicode support, since the PROBLEMS
entry is removed, should prefer UTF-8 more often. This would be the
best solution IMHO, as Gnus wouldn't have to contain magic charset
prioritizing code. It also seems like a reasonable solution, assuming
the Unicode stuff actually is working.
The simplest would probably be that people who likes Unicode run emacs
in a UTF-8 locale though, then they would not have any of these
problems.
Your RFC quote was interesting though, I think it suggests that Gnus
should downgrade UTF-8 to ISO-8859-X whenever possible, even if the
user uses a UTF-8 locale, since ISO-8859-X is more widely supported.
That would probably be a contentious decision though: What if a
Japanese user, in a UTF-8 locale, enters text that happens to be
downgradable to ISO-8859-1? Downgrading in this case is probably
never a good idea. OTOH if this situation is purely hypothetical, it
doesn't matter if downgrading happens.
next prev parent reply other threads:[~2003-03-08 20:09 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 ` Simon Josefsson [this message]
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=iluk7f9ipsd.fsf@latte.josefsson.org \
--to=jas@extundo.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).