From: Jesper Harder <harder@myrealbox.com>
Subject: Re: charset=macintosh
Date: Sun, 09 Mar 2003 04:56:44 +0100 [thread overview]
Message-ID: <m3adg5w5tv.fsf@defun.localdomain> (raw)
In-Reply-To: <iluheadipfb.fsf@latte.josefsson.org>
Simon Josefsson <jas@extundo.com> writes:
> But what if you are saying about UTF-8 clients being MIME capable is
> true, and since UTF-8 is typically never preferred by current emacsen,
> doesn't emacs' current guessing works the best we can hope for?
> Doesn't it detect among ISO-8859-X, ISO-2022 and Big5 properly?
No. I was hoping we could do something like this (for headers):
(let ((coding-systems (detect-coding-string string)))
(if (memq default coding-systems)
(decode-coding-string string default)
(decode-coding-string string (car coding-systems))))
i.e. if the default coding system is valid for the string, then use
that; otherwise use whatever Emacs thinks is the most likely coding
system. I think this would be ideal.
But unfortunately `detect-coding-string' _doesn't_ return a complete
list of possible coding systems. Consider this scenario:
I'm using Emacs in a Latin-1 locale. dk.* newsgroups work fine
because latin-1 is the default. But I also subscribe to, say, a few
Korean newsgroups. The entry in `gnus-groups-charset-alist':
("\\(^\\|:\\)han\\>" euc-kr)
should take care of selecting the proper default charset. But *oops*,
`detect-coding-string' doesn't think that euc-kr is a possible charset
for a Korean string encoded in euc-kr:
(detect-coding-string (encode-coding-string "안녕" 'euc-kr))
=> (iso-latin-1 iso-latin-1 raw-text japanese-shift-jis
chinese-big5 no-conversion)
So the above approach would fail.
> 2) Users with emacs in UTF-8 prefers UTF-8 too often, even when the
> data is invalid UTF-8 and another encoding should be selected.
>
> The second situation is a bug, and I hope we can fix this.
Yep, 2) is the most serious problem. Especially because more and more
people are (often unknowingly) using an UTF-8 locale because Redhat 8
switched to UTF-8 by default. Those people would experience Gnus as
broken when reading hierarchies like dk.* or de.*.
next prev parent reply other threads:[~2003-03-09 3:56 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 ` charset=macintosh Jesper Harder
2003-03-08 20:17 ` charset=macintosh Simon Josefsson
2003-03-09 3:56 ` Jesper Harder [this message]
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=m3adg5w5tv.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).