Good afternoon, Paul...
On Saturday 07 January 2006 07:59 am, you wrote:
> On Sat, 7 Jan 2006 06:27:35 -0800, Dave Laird <dlaird@xxxxxxxxxx> said:
> > > Then I guess it evals OK. Now can you turn on flyspell mode?
> >
> > Then I get the UTF-8 string not found error.
>
> Do you mean the "Invalid UTF-8 encoded string" error? That's
> caused by the default value of Ispell_Chars in ispell_init, which has
> latin1 characters in it. I should probably replace it with
>
> public variable Ispell_Letters = Assoc_Type[String_Type, "a-zA-Z"];
>
> I don't have an ispell or aspell that understands utf-8, but ispell.sl
> should probably work in utf-8 mode with just ascii characters, at least
> for English.
I replaced the existing "public variable Ispell_Letters" line with the
public variable above, and Ispell started working like a clock. The only
other rough edges are that once you highlight a word that is identified by
Ispell as not correct, the only options at the bottom of the page (the
mini-buffer?) are:
Enter choice. (^G to abort) (default: 0)
There is nothing about accepting the word this time or the means to
install the word into one's personal dictionary. I also noticed in
ispell_init, it creates a variable for Ispell. What happens if we change
that to read Aspell? I suspect it will break something, but I am truly
curious now. I am actually getting to where I can read the code in the Jed
libs, which is even more scary than the dictionary not working. 8-)
Dave
--
Dave Laird (Dave@xxxxxxxxxx)
The Used Kharma Lot / The Phoenix Project
An automatic & random fortune For the Minute from Unix fortunes:
prostitute is OVERCOOKING a LAMB CHOP!!
Attachment:
pgpnIbHP235Wh.pgp
Description: PGP signature