On Thu, Sep 13, 2007 at 09:29:09AM +0200, Vincent Lefevre wrote:
> Thanks for the idea. However, the dictionary for the whole buffer
> is often incorrect anyway,

While it would be nicer if done through xml:lang, you can always make sure
the whole buffer dict is correct by means of a right ispell-local-dictionary
entry in a local variables section.

<!-- Keep this comment at the end of the file
Local variables:
mode: sgml
ispell-local-dictionary: "american"
End:
-->

I suggest to use names that will be valid for both ispell and aspell, to
make your documents as portable as possible.

> and some of my files use mixed language
> (English/French). I wonder if something can be done on the Emacs
> side. I reported the following wishlit bug in the past:
> 
>   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=185488
> 
> but as you can see, ispell is no longer maintained in Debian (latest
> maintainer change in early 2004), and I now use aspell from Emacs.
> Perhaps a change in ispell.el could be sufficient, though.

I see,

[#185488] ispell: automatic dictionary selection for XML files (using xml:lang)

FYI, I know of a lisp package that tries to do that for flyspell,
flyspell-xml-multi.el, requiring ispell-multi.el. However, I never tried it.

There has been recently some discussion about integrating ispell-multi.el
functionality into ispell.el for future emacs23, along with
flyspell-xml-multi.el and flyspell-babel.el as separate files.

http://lists.gnu.org/archive/html/emacs-devel/2007-06/msg00840.html

But the expected work to make that ispell-multi.el integration fully
operative seems non-trivial, although general consensus is that it would
be a good thing. 

I do not know how current flyspell-xml-multi.el and ispell-multi.el
interact with current ispell.el and flyspell.el. However, you may want
to give them a try.

They are available from

http://www.dur.ac.uk/p.j.heslin/Software/Emacs/

Hope this helps,

-- 
Agustin



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to