Am 22.02.2005 um 02:29 schrieb Kenichi Handa:
At first, are you sure that you are using ispell.el distributed with CVS emacs?
Yes, I am. The header says:
;; Author: Ken Stevens <[EMAIL PROTECTED]> ;; Maintainer: Ken Stevens <[EMAIL PROTECTED]> ;; Stevens Mod Date: Mon Jan 7 12:32:44 PST 2003 ;; Stevens Revision: 3.6 ;; Status : Release with 3.1.12+ and 3.2.0+ ispell. ;; Bug Reports : [EMAIL PROTECTED] ;; Web Site : http://kdstevens.com/~stevens/ispell-page.html ;; Keywords: unix wp
Next, \x8e9 is a latin-1 character e-acute (latin-1 code is \351).
Yes, true. But why is GNU Emacs passing a character in that hex Unicode notation? Why can't it be the character it self as Carbon Emacs of the same src files does?
Are you sure that your "german" dictionally recognizes that character as word constituent?
Yes, it does! I can enter (French, Italian, Spanish, Swedish, Danish) words with accented characters into my personal dictionary and in Carbon Emacs, from the same source, they're correctly recognized.
At least, ispell.el in Emacs doesn't include that character in CASECHARS. Isn't there any good reason for not including it?
I am using them. Ispell can handle them, AFAIR. I don't write usually in US-ASCII 7bit. And since I use a modern TeX system I can type all characters as themselves, for example as UTF-8 in the file on disk, and this UTF-8 contents is then correctly processed in TeX. Usually the Latin-1 or Latin-9 subsets are sufficient for me right now, but I could start to write in Greek too: ÎáÏÎÎÎ. That's what our good old Archimedes once shouted and would like to shout myself when GNU Emacs 22 will do what I expect it to do.
-- Greetings
Pete
Either this man is dead or my watch has stopped. - Groucho Marx
_______________________________________________ Emacs-pretest-bug mailing list [email protected] http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
