Friday, November 7, 2008

Oracle Apex Spellchecker not working for you?
















If your a "textareas with spellchecker" look like this when you do a spellcheck, the solution is easily explained.

One of the parameters being passed is the language parameter, found in Shared Components > Edit Globalization Attributes.
In my case I have the language set to en-au (English - Australian). This is nice if you want your date-pickers to start the week on Mondays, but not so good for the spell-checker.

So how do we fix this?
It's just a case of populating the WWV_FLOW_DICTIONARY$ table for your language.
So for me the following script does it:
insert into wwv_flow_dictionary$ (language, owner, security_group_id, words, words_capitalized, words_soundex) select 'en-au', s.owner, s.security_group_id, s.words, s.words_capitalized, s.words_soundex from WWV_FLOW_DICTIONARY$ s where s.language = 'en-us'; commit;

Now if I was really being thorough, I'd go through all the words and fix the American spelling of words.
But after all, I am a developer and we're generally not known for our spelling :)

3 comments:

Jeffrey Kemp said...

duh! I only ever looked at the spellchecker once and dismissed it because I thought I'd have to prime it with a word list for it to be useful...

Thanks :)

Stirl said...

Thanks! I am also australian and have no dictionary...now if only i could get both to work...

Stirl said...

but for now its easier for me to simply change the application to a application that uses US english...