Am 12.10.2006 um 17:02 schrieb Richard Stallman:
Thanks for the detailed report, but an important set of details is
missing.
/usr/local/bin/emacs -Q <UTF-8 file #1> <UTF-8 file #2> &
For reliability in reproducing the bug, we need to know
the contents of both files. Send them uuencoded so that mail
cannot garble them.
The names could also matter, so please give the precise names.
If you sent all that in a previous message, please forgive my
faulty memory.
The files are 1.6 MB in size, each. The original one is for example:
http://ftp.funet.fi/pub/kermit/charsets/utf8.txt, the other one has
an extra header line
;;; -*- mode: Text; coding: utf-8; -*-
The recipe to create the other file is
echo ";;; -*- mode: Text; coding: utf-8; -*-" > utf8_txt
cat utf8.txt >> utf8_txt
So there is an obvious text file ``utf8.txt´´ without any Emacs
specific header line and one that is forced to be in text mode and in
UTF-8 encoding because of the header line, named ``utf8_txt´´.
I also have smaller UTF-8 files, but obviously it is at least needed
to have some Japanese (CJK?) characters in them (because the mode-
line starts with ``-E:--´´ for Japanese?). The error becomes visible
because subst-big5.el, subst-gb2312.el, subst-jis.el, and subst-
ksc.el are loaded.
--
Greetings
Pete
"Isn't vi that text editor with two modes... one that beeps and one
that corrupts your file?" -- Dan Jacobson, on comp.os.linux.advocacy
_______________________________________________
emacs-pretest-bug mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
