From: Dave Love <d.love@dl.ac.uk>
Cc: Kenichi Handa <handa@m17n.org>
Subject: Re: iso-8859-1 and non-latin-1 chars
Date: 06 Jan 2003 19:28:21 +0000 [thread overview]
Message-ID: <rzqr8bqcc2y.fsf@albion.dl.ac.uk> (raw)
In-Reply-To: 4207.1041354888@ichips.intel.com
Ken Stevens <kstevens@ichips.intel.com> writes:
> Ispell _does_ support multibyte characters. This was one of the
> historical reasons ispell.el did not use emacs syntax tables to
> determine word boundaries. (It supported latex words that included
> escape sequences such as \'{o}, etc.)
I didn't think that's really the same thing, but it's a long time
since I hacked on ispell. Also, I don't see why Emacs couldn't match
such words the same as ispell.
Anyhow, as I don't know, what does one have to do to create and use a
dictionary for utf-8 text? I could probably add support for that.
> I am not sure what it would take to support all the internal emacs
> encodings, or if this would be the best approach.
It is only _external_ encodings that are relevant, and perhaps only
utf-8. [I don't know if spell-checking actually makes sense in the
Oriental languages which typically use the multibyte iso-2022
encodings.]
Note that Emacs could cope now with checking utf-8-encoded text
against a dictionary for an 8-bit character set as long as the text
concerned can be encoded in that set. The text will be appropriately
encoded when it is sent to the subprocess. I think that really
requires using Emacs's (multibyte) syntax tables, though.
next prev parent reply other threads:[~2003-01-06 19:28 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-28 17:01 iso-8859-1 and non-latin-1 chars Dave Love
2002-12-02 15:47 ` Richard Stallman
2002-12-06 16:38 ` Dave Love
2002-12-09 6:08 ` Kenichi Handa
2002-12-15 16:24 ` Dave Love
2002-12-16 0:42 ` Kenichi Handa
2002-12-19 22:35 ` Dave Love
2002-12-23 6:40 ` Kenichi Handa
2002-12-23 12:27 ` Dave Love
2002-12-25 13:05 ` Kenichi Handa
2002-12-31 17:14 ` Ken Stevens
2003-01-06 19:28 ` Dave Love [this message]
2003-01-06 19:18 ` Dave Love
2003-01-07 13:01 ` Kenichi Handa
2003-01-10 10:59 ` Dave Love
2003-01-06 19:19 ` Dave Love
2002-12-16 14:06 ` Stefan Monnier
2002-12-19 22:33 ` Dave Love
2002-12-16 16:42 ` Richard Stallman
[not found] ` <E18LZqb-0007si-00@fencepost.gnu.org>
2002-12-15 16:25 ` Dave Love
2002-12-16 16:42 ` Richard Stallman
[not found] ` <E18LCz8-0004It-00@fencepost.gnu.org>
2002-12-10 23:47 ` Dave Love
2002-12-11 20:39 ` Richard Stallman
2002-12-13 2:58 ` Kenichi Handa
2002-12-14 18:31 ` Richard Stallman
2002-12-17 11:41 ` None Kenichi Handa
-- strict thread matches above, loose matches on Subject: below --
2002-11-07 14:57 iso-8859-1 and non-latin-1 chars Stefan Monnier
2002-11-07 15:25 ` Eli Zaretskii
2002-11-07 17:06 ` Stefan Monnier
2002-11-07 23:42 ` Kenichi Handa
2002-11-07 23:58 ` Stefan Monnier
2002-11-09 11:54 ` Richard Stallman
2002-11-09 20:32 ` Stefan Monnier
2002-11-11 10:19 ` Richard Stallman
2002-11-11 4:00 ` Kenichi Handa
2002-11-12 5:47 ` Richard Stallman
2002-11-18 0:08 ` Kenichi Handa
2002-11-18 19:09 ` Richard Stallman
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=rzqr8bqcc2y.fsf@albion.dl.ac.uk \
--to=d.love@dl.ac.uk \
--cc=handa@m17n.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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).