Richtext spell checker does not work with locale? | Community
Skip to main content
Community_Admin
Adobe Employee
Adobe Employee
October 16, 2015
Solved

Richtext spell checker does not work with locale?

  • October 16, 2015
  • 2 replies
  • 1057 views

We have created a site in cq with parent node as en_gb and try to use spell checker in richtext editor but it fails. Looking into the debug logs, it is looking for a dictionary as  en_gb_en_gb which does not exists and hence the spell checker does not work. Debugging further we found that the logic written in SpellCheckServlet & LanguageUtil seems to be incorrect as it returns language as en_gb & country also as en_gb rahter it should be lan= en & country = gb.

 

However, spell checker documentation says

 

The spelling checker will operate in the language of the website by taking either the language property of the subtree or extracting the language from the URL; i.e. the en branch will be checked for english, the de branch for german.

 

But both seems to fail.

 

Please suggest if there is something wrong in what I am doing or it is a bug in CQ?

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Community_Admin

Create your own servlet for cheking spelling as CQ does with API "com.day.cq.spellchecker".

 

And then add the servlet path to "spellcheck" plugin property.

Property name: spellcheckerUrl

Value : <servlet-path>

 

[Ref: http://dev.day.com/docs/en/cq/5-4/widgets-api/index.html?class=CQ.form .rte.plugins.SpellCheckerPlugin]

2 replies

Community_Admin
Adobe Employee
Community_AdminAdobe EmployeeAuthorAccepted solution
Adobe Employee
October 16, 2015

Create your own servlet for cheking spelling as CQ does with API "com.day.cq.spellchecker".

 

And then add the servlet path to "spellcheck" plugin property.

Property name: spellcheckerUrl

Value : <servlet-path>

 

[Ref: http://dev.day.com/docs/en/cq/5-4/widgets-api/index.html?class=CQ.form .rte.plugins.SpellCheckerPlugin]

October 16, 2015

This does not address the OP's question.  How has this been marked as solved?  To re-iterate, the question was: "Please suggest if there is something wrong in what I am doing or it is a bug in CQ?"

I am having the same issue and it sounds like a bug.  If there is a bug and therefore the only solution, rather than releasing a fix for the bug, is to create our own servlet to spellcheck, then that would be a clearer response, albeit a still mostly unhelpful response as this would then require knowledge on how to create a spellchecking servlet.