From: Kenichi Handa <handa@m17n.org>
Cc: emacs-devel@gnu.org
Subject: Re: iso-8859-1 and non-latin-1 chars
Date: Wed, 25 Dec 2002 22:05:29 +0900 (JST) [thread overview]
Message-ID: <200212251305.WAA15177@etlken.m17n.org> (raw)
In-Reply-To: <rzqr8c89ay9.fsf@albion.dl.ac.uk> (message from Dave Love on 23 Dec 2002 12:27:58 +0000)
In article <rzqr8c89ay9.fsf@albion.dl.ac.uk>, Dave Love <d.love@dl.ac.uk> writes:
> Kenichi Handa <handa@m17n.org> writes:
>> I don't think the program `ispell' itself should be fixed.
> I meant ispell.el, though it is unfortunate that we don't have a
> spelling program that deals with multibyte encodings as far as I know.
Sure. Though, I see this mail in linux-utf8 mailing list.
On Wed Feb 6 16:18:23 2002 +0300 Maxim N. Bychkov wrote:
>>Good day.
>>
>>Could anybody explain me how to use unicode symbols in Ispell?
>>
>>Thank you in advance.
>>
>
>AFAIK you can't. But some ispell dictionaries, like
>esperanto, have a hack for command line -Tutf8 option to
>spellcheck UTF-8 text.
>> But, ispell.el should be made more robust. When it finds an
>> unencodable character in a word, perhaps, it should show the
>> word as a misspelled word to a user instead of sending it to
>> the ispell program.
> Yes, that's what I've implemented for flyspell. The problem is that
> ispell.el sends a whole line to the subprocess (unlike flyspell).
> Also it doesn't use the Emacs syntax table to decide what's a word.
But, I think it's not that difficult to fix this behaviour
so that it breaks a line at an unencodable word.
>> Then BBDB should call select-safe-coding-system before
>> siliently using a specified coding system.
> No, it should use a general coding system to store all
> text.
If that is possible (i.e. users allows that), yes. But,
why calling select-safe-coding-system is not good?
> I implemented that, but people have used inappropriate
> values (either by setting the relevant variable or via
> `file-coding-system-alist') and there could be problems in
> the transition to the new version.
Those people should have already encountered a problem as I
wrote before because they can't decode a text back with the
same coding system.
By the way, the function choose_write_coding_system ()
checks a coding system specified in file-coding-system-alist
by select-safe-coding-system.
---
Ken'ichi HANDA
handa@m17n.org
next prev parent reply other threads:[~2002-12-25 13:05 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 [this message]
2002-12-31 17:14 ` Ken Stevens
2003-01-06 19:28 ` Dave Love
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=200212251305.WAA15177@etlken.m17n.org \
--to=handa@m17n.org \
--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 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).