[geeklog-devtalk] geeklog-devel digest, Vol 1 #234 - 1 msg

geeklog-devel-request at lists.geeklog.net geeklog-devel-request at lists.geeklog.net
Thu Dec 4 13:00:10 EST 2003


Send geeklog-devel mailing list submissions to
geeklog-devel at lists.geeklog.net

To subscribe or unsubscribe via the World Wide Web, visit
http://lists.geeklog.net/listinfo/geeklog-devel
or, via email, send a message with subject or body 'help' to
geeklog-devel-request at lists.geeklog.net

You can reach the person managing the list at
geeklog-devel-admin at lists.geeklog.net

When replying, please edit your Subject line so it is more specific
than "Re: Contents of geeklog-devel digest..."


Today's Topics:

1. Re: Spelling interface ready for testing... (Tony Bibbs)

--__--__--

Message: 1
Date: Wed, 03 Dec 2003 19:54:25 -0600
From: Tony Bibbs <tony at tonybibbs.com>
To: geeklog-devel at lists.geeklog.net
Subject: Re: [geeklog-devel] Spelling interface ready for testing...
Reply-To: geeklog-devel at lists.geeklog.net



> I was not sure if I would see it when in story editor creating a

> story. I saw it highlight my test bad words after I posted it and

> tried to edit it.

> No indication before that.


Yeah, the easiest way to integrate it now is to change the 'preview'
button to say something like 'preview/spellcheck' or something like
that. In this manner we end up reusing must of what we already have. I
open to suggestions. My goes was to make as little impace on this as
possible. If you wanted, we could make the save logic good enough to
give a warning when errors are found but that would be more work. What
I absolutely don't want to get into is popping up windows to handle
spellchecking...that's more a matter of peronal opinion.


>

> Now this was just a quick initial test. I entered this for my test:

>

> thi is a tst

> helo dos this worke

>

I'll have to test this. The class, by default, should not spell check
words less than 3 characters long. I think with your example this must
not be working as you noted it flaged the 'is' on the first line. As
for the second line, it's another bug. Once it finds the bugs it does a
str_replace() to put the span's in and my hunch is that i'm doing a
str_replace() on 'is' instead of ' is ' (note the spaces).

As for why it didn't catch the otherwords, I'm a bit at a loss, let me
try it on my XP box and see if I get the same thing. More to come soon.



--__--__--

_______________________________________________
geeklog-devel mailing list
geeklog-devel at lists.geeklog.net
http://lists.geeklog.net/listinfo/geeklog-devel


End of geeklog-devel Digest



More information about the geeklog-devtalk mailing list