From: Kenichi Handa <handa@m17n.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: bug-gnu-emacs@gnu.org, 1187@emacsbugs.donarmstrong.com
Subject: bug#1187: 23.0.60; Cannot read vline.el - invalid read syntax
Date: Tue, 21 Oct 2008 11:40:42 +0900 [thread overview]
Message-ID: <E1Ks7Ao-0004ud-Hy@etlken.m17n.org> (raw)
In-Reply-To: <uy70jilch.fsf@gnu.org> (message from Eli Zaretskii on Mon, 20 Oct 2008 12:58:54 +0200)
In article <uy70jilch.fsf@gnu.org>, Eli Zaretskii <eliz@gnu.org> writes:
> It's vline.el, and you can download it from here:
> http://www.emacswiki.org/cgi-bin/wiki/vline.el
> (It is better to download, to avoid any possible transformations of
> the file in mail transfer.)
Ok, I found what is the problem. In Emacs 22, iso-8859-1 is
a coding of type `iso-2022', but in Emacs 23, it's of type
`charset', and I forgot to handle latin-extra-code-table
(which has nil for the byte 0x80) in the detector of that
kind of coding system. As I've just installed a fix, the
latest code should detect vline.el correctly as utf-8.
But, the reason why it's detected as utf-8 is because the
file contains a byte 0x80. If a file doesn't contain a byte
in the range 0x80..0x9F and nil in latin-extra-code-table,
it's impossible to distinguish iso-latin-1 from utf-8.
So, in general, it's a good idea to add coding-tag: utf-8
for utf-8 files.
---
Kenichi Handa
handa@ni.aist.go.jp
next prev parent reply other threads:[~2008-10-21 2:40 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <jwv3aivjkhw.fsf-monnier+emacsbugreports@gnu.org>
2008-10-16 21:22 ` bug#1187: 23.0.60; Cannot read vline.el - invalid read syntax Drew Adams
2008-10-16 23:41 ` Lennart Borgman (gmail)
2008-10-17 0:00 ` Drew Adams
2008-10-17 8:18 ` Eli Zaretskii
2008-10-17 8:36 ` Lennart Borgman (gmail)
2008-10-17 9:57 ` Eli Zaretskii
2008-10-17 8:15 ` Eli Zaretskii
2008-10-17 14:26 ` Drew Adams
2008-10-17 12:30 ` Lawrence Mitchell
2008-10-17 13:07 ` Eli Zaretskii
2008-10-17 14:40 ` Drew Adams
2008-10-17 15:53 ` Drew Adams
2008-10-17 16:04 ` Eli Zaretskii
2008-10-17 14:58 ` Lennart Borgman (gmail)
2008-10-17 15:18 ` Drew Adams
2008-10-17 15:58 ` Lawrence Mitchell
2008-10-17 16:09 ` Drew Adams
2008-10-17 16:00 ` Eli Zaretskii
2008-10-17 16:21 ` Drew Adams
2008-10-17 18:24 ` Eli Zaretskii
2008-10-20 10:28 ` Kenichi Handa
2008-10-20 10:58 ` Eli Zaretskii
2008-10-21 2:40 ` Kenichi Handa [this message]
2008-10-21 4:46 ` Drew Adams
2008-10-17 15:55 ` bug#1187: marked as done (23.0.60; Cannot read vline.el - invalid read syntax) Emacs bug Tracking System
[not found] ` <handler.1187.D1187.122425837312105.notifdone@emacsbugs.donarmstrong.com>
2008-10-17 16:48 ` bug#1187: closed by Stefan Monnier <monnier@iro.umontreal.ca> (Re: bug#1187: 23.0.60; " 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=E1Ks7Ao-0004ud-Hy@etlken.m17n.org \
--to=handa@m17n.org \
--cc=1187@emacsbugs.donarmstrong.com \
--cc=bug-gnu-emacs@gnu.org \
--cc=eliz@gnu.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.
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).