From: Jason Rumney <jasonr@f2s.com>
To: Eli Zaretskii <eliz@gnu.org>, 2497@emacsbugs.donarmstrong.com
Cc: uwe.siart@tum.de, David Engster <deng@randomsample.de>
Subject: bug#2497: 23.0.91; Fails to read UTF-8 on Win2k
Date: Sat, 28 Feb 2009 22:16:22 +0800 [thread overview]
Message-ID: <49A94736.5000206@f2s.com> (raw)
In-Reply-To: <u3adypxun.fsf@gnu.org>
Eli Zaretskii wrote:
> You are right. But in my case, it was not enough to test for
> "iso-8859-", as the symbol's name was "iso-latin-1", not "iso-8859-1".
>
> I installed the patch below, that does seem to fix the problem with
> the OP's .gnus.el, although I don't know how general that problem is,
> nor whether Emacs is capable of distinguishing UTF-8 from Latin-N in
> general.
>
I installed a further change for the case where latin-extra-code-table
is not a vector. But I don't understand why we have this table, and why
the default value allows the 6 C1 control codes PU1, PU2, STS, CCH, MW
and SPA to appear in latin text without breaking the auto detection. Are
these control characters really that common?
next prev parent reply other threads:[~2009-02-28 14:16 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <uzlg6oiq3.fsf@gnu.org>
2009-02-17 10:35 ` bug#2354: 23.0.90; Emacs fails to detect utf-8 encoding with language environment Latin-1 David Engster
2009-02-17 16:45 ` Juanma Barranquero
2009-02-17 18:04 ` David Engster
2009-02-28 12:30 ` bug#2354: marked as done (23.0.90; Emacs fails to detect utf-8 encoding with language environment Latin-1) Emacs bug Tracking System
2009-02-27 14:10 ` bug#2497: 23.0.91; Fails to read UTF-8 on Win2k Uwe Siart
2009-02-27 16:03 ` Eli Zaretskii
2009-02-27 16:48 ` Uwe Siart
2009-02-27 18:19 ` Eli Zaretskii
2009-02-27 20:35 ` Uwe Siart
2009-02-28 4:40 ` Stefan Monnier
2009-02-28 8:17 ` Uwe Siart
2009-02-28 10:14 ` David Engster
2009-02-28 12:09 ` Eli Zaretskii
2009-02-28 14:16 ` Jason Rumney [this message]
2009-02-28 14:31 ` David Engster
2009-02-28 22:00 ` Stefan Monnier
2009-02-28 10:49 ` Eli Zaretskii
2009-02-28 12:16 ` Uwe Siart
2009-02-28 22:04 ` Stefan Monnier
2009-03-02 11:43 ` Kenichi Handa
2009-03-02 15:25 ` Stefan Monnier
2009-03-02 19:25 ` Eli Zaretskii
2009-03-03 16:34 ` Stefan Monnier
2009-02-27 16:11 ` Juanma Barranquero
2009-02-27 16:16 ` Juanma Barranquero
2009-02-27 16:27 ` Uwe Siart
2009-02-27 16:32 ` Juanma Barranquero
2009-02-27 16:23 ` Uwe Siart
2009-02-27 16:38 ` Juanma Barranquero
2009-02-27 18:19 ` Eli Zaretskii
2009-02-27 20:38 ` Juanma Barranquero
2009-02-28 1:29 ` Jason Rumney
2009-02-27 17:02 ` Leo
2009-02-27 17:46 ` David Engster
2009-02-27 21:15 ` Uwe Siart
2009-02-28 1:32 ` Jason Rumney
2009-02-28 1:35 ` Processed (with 5 errors): " Emacs bug Tracking System
2009-02-27 23:34 ` bug#2497: 23.0.91; Fails to read UTF-8 on Windows2k Richard M Stallman
2009-02-28 9:47 ` Uwe Siart
2009-02-28 18:08 ` Richard M Stallman
2009-02-28 12:30 ` bug#2497: marked as done (23.0.91; Fails to read UTF-8 on Win2k) Emacs bug Tracking System
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=49A94736.5000206@f2s.com \
--to=jasonr@f2s.com \
--cc=2497@emacsbugs.donarmstrong.com \
--cc=deng@randomsample.de \
--cc=eliz@gnu.org \
--cc=uwe.siart@tum.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).