all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: martin rudalics <rudalics@gmx.at>
To: Agustin Martin <agustin.martin@hispalinux.es>
Cc: emacs-devel@gnu.org
Subject: Re: Adding ispell-multi.el and friends to Emacs
Date: Wed, 20 Jun 2007 14:46:03 +0200	[thread overview]
Message-ID: <4679218B.60504@gmx.at> (raw)
In-Reply-To: <20070619131400.GA10763@agmartin.aq.upm.es>

 >>FWIW, I have misalignment clashes only when Emacs and the spell system
 >>disagree about the coding system.  In that case, however, the output
 >>of the spell system is unusable for single words too.
 >
 >
 > Unless communication is done in utf8, if you have an utf8 buffer with a char
 > not in the dict charset ispell-region will fail with a misalingment (at
 > least with ispell, most aspell communications are done in utf8), but if you
 > try ispell-word in that word, the foreign char will not be recognized as
 > part of a word and only part of it will be sent to ispell for testing. The
 > difference is that ispell-region will fail for all the region if a
 > misalignment appear while ispell-word will only do things differently for
 > the affected word. That was the intention.

Personally, I don't care whether a word, line, region or buffer appears
corrupted.  I'd discontinue spell-checking in any of these cases.  The
interface (ispell.el) has to check which coding system should get
applied.  The user has to check whether the interface got it right and,
if necessary, be able to override wrong settings.  BTW, I don't use utf8
to communicate with Aspell and did not encounter any problems so far.

  reply	other threads:[~2007-06-20 12:46 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-14 12:58 Adding ispell-multi.el and friends to Emacs Peter Heslin
2007-06-15  8:48 ` Richard Stallman
2007-06-15 23:00   ` Peter Heslin
2007-06-16 18:50     ` Richard Stallman
2007-06-16 19:46       ` Frank Schmitt
2007-06-17 21:05         ` Agustin Martin
2007-06-17 21:31           ` Juri Linkov
2007-06-17 23:11             ` Peter Heslin
2007-06-18  9:55               ` Agustin Martin
2007-06-18 12:35                 ` martin rudalics
2007-06-19 13:14                   ` Agustin Martin
2007-06-20 12:46                     ` martin rudalics [this message]
2007-06-20 23:09                       ` Agustin Martin
2007-06-21 18:44                 ` Davis Herring
2007-06-18 21:31               ` Richard Stallman
2007-06-15  9:21 ` martin rudalics
2007-06-15 22:53   ` Peter Heslin
2007-06-16 10:03     ` martin rudalics
2007-06-16 10:55     ` Eli Zaretskii
2007-06-16 12:24       ` martin rudalics
2007-06-18 10:02     ` Agustin Martin
2007-06-18 12:37       ` martin rudalics
2007-06-19 15:13         ` Agustin Martin
2007-06-20 12:47           ` martin rudalics
2007-06-20 23:33             ` Agustin Martin
2007-06-21 17:32               ` Richard Stallman
2007-06-21 17:59                 ` David Kastrup
2007-06-21 21:39                 ` Peter Heslin
2007-06-22 16:24                   ` Richard Stallman
2007-06-22 21:22                     ` Peter Heslin
2007-06-23 18:26                       ` Richard Stallman
2008-01-13 17:19                         ` Dan Nicolaescu
2007-06-21 21:25               ` Peter Heslin

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4679218B.60504@gmx.at \
    --to=rudalics@gmx.at \
    --cc=agustin.martin@hispalinux.es \
    --cc=emacs-devel@gnu.org \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.