From: Oliver Scholz <alkibiades@gmx.de>
Subject: Re: [newbie] emacs flyspell not understands well accented chars
Date: Mon, 02 Jun 2003 13:14:33 +0200 [thread overview]
Message-ID: <ubrxgivdy.fsf@ID-87814.user.dfncis.de> (raw)
In-Reply-To: 84znl0ubx6.fsf@lucy.is.informatik.uni-duisburg.de
kai.grossjohann@gmx.net (Kai Großjohann) writes:
> "Eli Zaretskii" <eliz@elta.co.il> writes:
>
>> I suspect this is because your locale sets Emacs up to use Latin-9
>> encoding, while Ispell's dictionary is encoded in Latin-1. Current
>> released versions of Emacs see Latin-1 and Latin-9 as different
>> characters, sigh...
>
> It's fairly easy to fool ispell. I use the following kludge:
>
> (require 'ispell)
> (add-to-list 'ispell-local-dictionary-alist
> '("ndeutsch8-15"
> "[a-zA-Z\xf44\xf56\xf5c\xf5f\xf64\xf76\xf7c]"
> "[^a-zA-Z\xf44\xf56\xf5c\xf5f\xf64\xf76\xf7c]"
> "[']" t
> ("-C" "-d" "ndeutsch")
> "~latin1" iso-8859-15))
>
> I took the ndeutsch8 entry and modified it slightly. Note that the
> next-to-last item still says "~latin1", and the ispell dictionary
> name still says "ndeutsch", but the last item in the list is now
> iso-8859-15 instead of iso-8859-1.
[...]
I suspect (but have not tested it) that if the OP replaces the two
regexps with "[[:alpha:]]" and "[^[:alpha:]]" respectively, it could
work right of the box with Italian, too.
Oliver
--
14 Prairial an 211 de la Révolution
Liberté, Egalité, Fraternité!
next prev parent reply other threads:[~2003-06-02 11:14 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-01 17:28 [newbie] emacs flyspell not understands well accented chars Mario Giammarco
2003-06-01 18:27 ` Eli Zaretskii
[not found] ` <mailman.7104.1054492093.21513.help-gnu-emacs@gnu.org>
2003-06-01 18:57 ` Ole Laursen
2003-06-01 19:08 ` Stefan Monnier
2003-06-01 20:27 ` Mario Giammarco
2003-06-01 20:02 ` Mario Giammarco
2003-06-02 8:21 ` Kai Großjohann
2003-06-02 11:14 ` Oliver Scholz [this message]
2003-06-02 12:09 ` Mario Giammarco
2003-06-02 13:53 ` Oliver Scholz
2003-06-02 15:30 ` Mario Giammarco
2003-06-02 16:54 ` Oliver Scholz
2003-06-02 17:11 ` Mario Giammarco
2003-06-02 17:39 ` Oliver Scholz
2003-06-03 8:31 ` Mario Giammarco
2003-06-03 12:52 ` Oliver Scholz
2003-06-03 13:39 ` Mario Giammarco
2003-06-03 14:53 ` Oliver Scholz
2003-06-03 18:21 ` Mario Giammarco
2003-06-03 19:57 ` Oliver Scholz
2003-06-03 20:32 ` Mario Giammarco
2003-06-04 17:43 ` Mario Giammarco
2003-06-04 21:32 ` Oliver Scholz
2003-06-05 12:01 ` Mario Giammarco
2003-06-05 12:17 ` Mario Giammarco
2003-06-05 22:21 ` Oliver Scholz
2003-06-06 8:33 ` Mario Giammarco
2003-06-06 11:09 ` Oliver Scholz
2003-06-06 12:27 ` Mario Giammarco
2003-06-06 12:52 ` Oliver Scholz
2003-06-06 13:28 ` Mario Giammarco
2003-06-06 13:40 ` Oliver Scholz
2003-06-06 14:01 ` Mario Giammarco
2003-06-07 10:16 ` Reiner Steib
2003-06-07 12:18 ` Mario Giammarco
2003-06-06 12:42 ` Mario Giammarco
2003-06-03 19:20 ` Stefan Monnier
2003-06-02 17:18 ` Mario Giammarco
2003-06-02 17:40 ` Oliver Scholz
2003-06-03 8:32 ` Mario Giammarco
2003-06-03 12:36 ` Oliver Scholz
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=ubrxgivdy.fsf@ID-87814.user.dfncis.de \
--to=alkibiades@gmx.de \
/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.
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).