| 7 | | If your webserver does not have a recent version of aSpell installed you will have problems due to unicode characters (typically in utf8 encoding) not being "understood" by aspell (aspell doesn't support Unicode at all really, but later versions won't do quite such strange things). Because getting aspell updated on servers can be a bit of a pain, you can download a ready-compiled aspell version here, just extract this into your SpellChecker plugin directory (all the files will be in SpellChecker/aspell), this compiled version is only suitable for x86 Linux machines. |
| | 7 | '''Using the PHP backend is the default, and recommended, the PERL backend is not currently maintained.''' |
| | 8 | |
| | 9 | == aSpell == |
| | 10 | |
| | 11 | If your webserver does not have a recent version of aSpell installed you will have problems due to unicode characters (typically in utf8 encoding) not being "understood" by aspell (aspell doesn't support Unicode at all really, but later versions won't do quite such strange things). |
| | 12 | |
| | 13 | === Precompiled Version === |
| | 14 | |
| | 15 | Because getting aspell updated on servers can be a bit of a pain, you can download a ready-compiled aspell version here, just extract this into your SpellChecker plugin directory (all the files will be in SpellChecker/aspell), this compiled version is only suitable for x86 Linux machines. |
| | 16 | |
| | 17 | As long as you are using the PHP backend for SpellChecker (default) then it will pickup the presence of the local aspell and use that instead of any other version installed on the server. |