Kenichi Handa <[EMAIL PROTECTED]> writes:
> PS. I personally feel it's a waste of time to struggle with
> charset matters in ispell that much because emacs-unicode
> should not have such a problem.
Oh, but in the 5+ years until it gets released, people might still be
glad to have a fix.
--
Davi
In article <[EMAIL PROTECTED]>, Juri Linkov <[EMAIL PROTECTED]> writes:
> Now a new problem was uncovered: after selecting a correct word from
> a list of near misses returned from ispell, ispell.el replaces the
> misspelled word with a selected word, and inserts it into the buffer
> not in its ori
> This approach is quite promising, but it doesn't work sufficiently well
> for non-English languages. It loses all characters that don't belong
> to the alphabet specified in .aff file. For example, it turns the line:
For related reasons, the english.aff file in the next ispell release
will inc
Geoff Kuenning <[EMAIL PROTECTED]> writes:
> Just brainstorming, it probably wouldn't be too hard to write a
> postprocessing script for -a mode that turned the output of ispell -a
> into something suitable for another ispell.
This approach is quite promising, but it doesn't work sufficiently well
Kenichi Handa <[EMAIL PROTECTED]> writes:
> In article <[EMAIL PROTECTED]>, Juri Linkov <[EMAIL PROTECTED]> writes:
>> The cause of the error is the following: a line sent by ispell.el
>> to the ispell process is converted from mule-unicode charset to the
>> process charset, and the accepted output
In article <[EMAIL PROTECTED]>, Juri Linkov <[EMAIL PROTECTED]> writes:
> Kenichi Handa <[EMAIL PROTECTED]> writes:
>> Please try the latest ispell.el. I think at least this
>> misalignment error is fixed now.
> I tried the latest ispell.el and I see that your change is a definite
> improvemen
> I agree that marking would help ispell.el to decide which dictionary
> to use on a word. However, even without marking users might still prefer
> to check words simultaneously with multiple dictionaries
That's a good point. Unfortunately, the current implementation of
ispell makes it impossibl
Kenichi Handa <[EMAIL PROTECTED]> writes:
> Please try the latest ispell.el. I think at least this
> misalignment error is fixed now.
I tried the latest ispell.el and I see that your change is a definite
improvement since it now allows to check words in mule-unicode charsets.
But it still doesn't
In article <[EMAIL PROTECTED]>, David Kastrup <[EMAIL PROTECTED]> writes:
>>> If ispell wants utf-8, it's easy enough to convert each input line to
>>> utf-8 and deal with offsets into that in the event of a mispelling;
>>
>> Or account for byte offsets by (variable) multibyte lenght of each
>>
In article <[EMAIL PROTECTED]>, Juri Linkov <[EMAIL PROTECTED]> writes:
> Agustin Martin <[EMAIL PROTECTED]> writes:
>> *Ken*, since you are being cc'ed I vaguely remembered some info I somewhere
>> read about this misalignements. I finally found it,
>>
>> http://lists.gnu.org/archive/html/em
In article <[EMAIL PROTECTED]>, Richard Stallman <[EMAIL PROTECTED]> writes:
> People have been discussing this issue for a while now,
> and due to the volume of mail, I could not read it all.
I'm reading it, and I think I understand what is the
problem.
> Handa, is it clear what we should do no
In article <[EMAIL PROTECTED]>, Agustin Martin <[EMAIL PROTECTED]> writes:
> I meant with oe-1char oe as a single char (U+0153), available
> in iso-8859-15 (octal \275 here), but not in iso-8859-1 (you
> have one half instead), and with oe-2char the two 7bit chars sequence
> 'oe', available anywher
On Tue, Jan 11, 2005 at 08:56:23PM +0100, Agustin Martin wrote:
> The french dict is originally latin1 and use the two chars sequence
> 'oe', although the Debian dict defines single-chars 'oe' and 'OE' at
> the default stringchars section, but did not use inside.
I'm not sure what you mean with "
On Tue, Jan 11, 2005 at 02:16:33PM +0900, Kenichi Handa wrote:
> In article <[EMAIL PROTECTED]>, Agustin Martin <[EMAIL PROTECTED]> writes:
>
> Sorry I don't understand. What is oe-1char? U+0153 or
> U+0276? But, neither of them are not included in
> iso-8859-1/iso-8859-15? And, I have no ide
People have been discussing this issue for a while now,
and due to the volume of mail, I could not read it all.
Handa, is it clear what we should do now for the coming release?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
In article <[EMAIL PROTECTED]>, Agustin Martin <[EMAIL PROTECTED]> writes:
> (Handa, your patch worked better than I thought, read below)
Thank you, that's a good news.
> Also Kenichi Handa provided us with a patch to ensure that all equivalent
> accented chars are mapped to the same char, if av
> Cc: [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED],
> [EMAIL PROTECTED], [EMAIL PROTECTED],
> [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED]
> From: David Kastrup <[EMAIL PROTECTED]>
> Date: Mon, 10 Jan 2005 10:09:41 +0100
>
> Just encode the line to utf-8,
(Handa, your patch worked better than I thought, read below)
On Mon, Jan 10, 2005 at 02:06:41PM +0100, Lionel Elie Mamane wrote:
> On Wed, Dec 22, 2004 at 06:13:06PM +0100, Agustin Martin wrote:
> > So the only language that might currently require extra work is
> > french, and for it I find reaso
On Wed, Dec 22, 2004 at 06:13:06PM +0100, Agustin Martin wrote:
> On Wed, Dec 22, 2004 at 09:37:32PM +0900, Kenichi Handa wrote:
> Thanks for the tip. I am not maintaining emacs, but a package for
> the common dictionaries setup (dictionaries-common) that provides a
> recent and patched ispell.el
"Eli Zaretskii" <[EMAIL PROTECTED]> writes:
>> Date: Sat, 8 Jan 2005 22:29:21 +0900
>> From: Miles Bader <[EMAIL PROTECTED]>
>> Cc: Geoff Kuenning <[EMAIL PROTECTED]>, [EMAIL PROTECTED],
>> [EMAIL PROTECTED], [EMAIL PROTECTED],
>> Kenichi Handa <[EMAIL PROTECTED]>, [EMAIL PROTECTED],
>>
20 matches
Mail list logo
