Jose Figueroa-O'Farrill
j.m.f****@ed*****
Wed Sep 14 20:37:17 JST 2005
Hi,
Just to update you on my coding problems. They were due to a call to
the "semi-obsolete" function 'standard-display-european' which had
remained in my .emacs file long after I remembered what it was there
for.
However I now have problems with Ispell. I'm using the built-in
aspell, but I added a French dictionary to the dictionary directory.
It was working before, but now it does not recognise the accents.
For example in a buffer with coding system iso-8859-1, the word
"Amérique" is not understood. I get the error:
ispell-process-line: Ispell misalignment: word `érique' point 557;
probably incompatible versions
I also noticed that the e-acute becomes an E-grave when I send email
using VM. It never happened before. I think that this happens when
VM MIME encodes the message.
I have no settings at all in my .emacs file concerning coding. The
current buffer is a VM Mail folder and the output of M-x
describe-current-coding-system is
Coding system for saving this buffer:
t -- raw-text-unix
Default coding system (for new files):
1 -- iso-latin-1 (alias: iso-8859-1 latin-1)
Coding system for keyboard input:
M -- mac-roman
Coding system for terminal output:
1 -- iso-8859-1 (alias of iso-latin-1)
Defaults for subprocess I/O:
decoding: 1 -- iso-latin-1 (alias: iso-8859-1 latin-1)
encoding: 1 -- iso-latin-1 (alias: iso-8859-1 latin-1)
Priority order for recognizing coding systems when reading files:
1. iso-latin-1 (alias: iso-8859-1 latin-1)
2. mule-utf-8 (alias: utf-8)
3. mule-utf-16be-with-signature (alias: utf-16be-with-signature mule-utf-16-be utf-16-be)
4. mule-utf-16le-with-signature (alias: utf-16le-with-signature mule-utf-16-le utf-16-le)
5. iso-2022-jp (alias: junet)
6. iso-2022-7bit
7. iso-2022-7bit-lock (alias: iso-2022-int-1)
8. iso-2022-8bit-ss2
9. emacs-mule
10. raw-text
11. japanese-shift-jis (alias: shift_jis sjis cp932)
12. chinese-big5 (alias: big5 cn-big5 cp950)
13. no-conversion
Other coding systems cannot be distinguished automatically
from these, and therefore cannot be recognized automatically
with the present coding system priorities.
The following are decoded correctly but recognized as iso-2022-7bit-lock:
iso-2022-7bit-ss2 iso-2022-7bit-lock-ss2 iso-2022-cn iso-2022-cn-ext
iso-2022-jp-2 iso-2022-kr
Particular coding systems specified for certain file names:
OPERATION TARGET PATTERN CODING SYSTEM(s)
--------- -------------- ----------------
File I/O "\\.dz\\'" (no-conversion . no-conversion)
"\\.g?z\\(~\\|\\.~[0-9]+~\\)?\\'"
(no-conversion . no-conversion)
"\\.tgz\\'" (no-conversion . no-conversion)
"\\.tbz\\'" (no-conversion . no-conversion)
"\\.bz2\\'" (no-conversion . no-conversion)
"\\.Z\\(~\\|\\.~[0-9]+~\\)?\\'"
(no-conversion . no-conversion)
"\\.elc\\'" (emacs-mule . emacs-mule)
"\\.utf\\(-8\\)?\\'" utf-8
"\\(\\`\\|/\\)loaddefs.el\\'"
(raw-text . raw-text-unix)
"\\.tar\\'" (no-conversion . no-conversion)
"\\.po[tx]?\\'\\|\\.po\\."
po-find-file-coding-system
"\\.\\(tex\\|ltx\\|dtx\\|drv\\)\\'"
latexenc-find-file-coding-system
"" (undecided)
Process I/O nothing specified
Network I/O nothing specified
Thanks again,
José