From: Kenichi Handa <handa@m17n.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: tlikonen@iki.fi, 3607@emacsbugs.donarmstrong.com
Subject: bug#3607: 23.0.94; odd character in fringe.el
Date: Mon, 29 Jun 2009 20:39:34 +0900 [thread overview]
Message-ID: <E1MLFCw-00023e-Nb@etlken> (raw)
In-Reply-To: <jwv63ef4e6w.fsf-monnier+emacsbugreports@gnu.org> (message from Stefan Monnier on Mon, 29 Jun 2009 10:52:20 +0200)
In article <jwv63ef4e6w.fsf-monnier+emacsbugreports@gnu.org>, Stefan Monnier <monnier@iro.umontreal.ca> writes:
> Actually, AFAIK the "unlikely false positives" property of the utf-8
> encoding is not only true when applied to latin-1 files but also to most
> other encodings. So really utf-8 should probably always be first (not
> only for latin-1 environments), except maybe for some envs where there's
> a knows non-negligible risk of false positives.
I think it's only Latin-X (and perhaps Vietnamese too) that
are mostly safe to give utf-8 the higher priority on code
detection, because only they use Latin script in which 8-bit
characters rarely appear succeedingly.
---
Kenichi Handa
handa@m17n.org
next prev parent reply other threads:[~2009-06-29 11:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.888.1245349050.2239.bug-gnu-emacs@gnu.org>
2009-06-18 18:41 ` bug#3607: 23.0.94; odd character in fringe.el Teemu Likonen
2009-06-18 18:54 ` Drew Adams
2009-06-18 19:20 ` Teemu Likonen
2009-06-18 21:08 ` Drew Adams
2009-06-18 21:34 ` Lennart Borgman
2009-06-19 0:47 ` Kenichi Handa
2009-06-27 1:07 ` Stefan Monnier
2009-06-27 1:25 ` Kenichi Handa
2009-06-27 21:44 ` Stefan Monnier
2009-06-29 7:49 ` Kenichi Handa
2009-06-29 8:52 ` Stefan Monnier
2009-06-29 11:39 ` Kenichi Handa [this message]
2009-06-29 18:16 ` Eli Zaretskii
2009-06-29 20:48 ` Stefan Monnier
2009-06-18 18:00 Drew Adams
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=E1MLFCw-00023e-Nb@etlken \
--to=handa@m17n.org \
--cc=3607@emacsbugs.donarmstrong.com \
--cc=monnier@iro.umontreal.ca \
--cc=tlikonen@iki.fi \
/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).