After reading the docs for both spellerpages and aspell, and following a few hours of hacking at the spellchecker.cfm, I finally managed to get the spellchecker to work.
Now I'm very disapointed because all I can do is go through my list of typos, get a list of suggestion and pick one, and ... that's about it. There's no way to send the text back to the editor. I can't even see a mention of that in the code. So a user would have to manually correct his errors after spotting them in the spellchecker.
To top it off I had to strip the html marking out of the text sent to aspell to avoid the tags getting flagged as typos and/or big issues with the display of the said tags within speller pages. In a nusthell you can't have html within speller pages when validating, it makes the text unreadable.
Since 1) it doesn't work at all out the box and 2) it doesn't work properly even when you spend hours fixing it, my question is:
Was it even meant to make it in this release? I'm not unhappy having to fix a few bugs on my own in other sections of the code, but this one is just too buggy too warrant its inclusion in the release. Please let me know if I'm missing something (I hope so).
Cheers,
Stephan.
Now I'm very disapointed because all I can do is go through my list of typos, get a list of suggestion and pick one, and ... that's about it. There's no way to send the text back to the editor. I can't even see a mention of that in the code. So a user would have to manually correct his errors after spotting them in the spellchecker.
To top it off I had to strip the html marking out of the text sent to aspell to avoid the tags getting flagged as typos and/or big issues with the display of the said tags within speller pages. In a nusthell you can't have html within speller pages when validating, it makes the text unreadable.
Since 1) it doesn't work at all out the box and 2) it doesn't work properly even when you spend hours fixing it, my question is:
Was it even meant to make it in this release? I'm not unhappy having to fix a few bugs on my own in other sections of the code, but this one is just too buggy too warrant its inclusion in the release. Please let me know if I'm missing something (I hope so).
Cheers,
Stephan.
RE: spell checker
It DOES send the user back to the editor page + copy the content back to the editor, but on IE 60 only, not Firefox 106.
Stephan.
RE: spell checker
Running on Linux - Apache with the "spellchecker.pl" spell check script.
RE: spell checker
The only difference is the behaviour with some html entities ( ) an br-tags, they are shown in text.
And I also had to do some modifications.
cheers
jenzener
RE: spell checker
However, the point I'm getting to is, the spell checker should either works or not, there is not in-between. So there is little point for me to spend hours fixing it up if the best I can get is "some html entities ( ) an br-tags, they are shown in text.". Did you manage to get past those hurdles?
Thanks,
Stephan.
RE: spell checker
Actually I'll update my post since an example is worth a thousand words:
Look at: http://www.dynarch.com/demos/htmlarea/e ... ecker.html
it's using aspell as well, and it feels like the js code was 'inspired' by speller pages.
What's interesting is how the spell check is ignoring the html markup for the spell check, yet displaying it properly formatted in the spell check window, and finallly updating the edition window with the corrected words AND the HTML back in. .
Does anyone know if this this possible with fck?
cheers,
Stephan.
RE: spell checker
RE: spell checker
Cheers,
Stephan.