Editor spell checking

[Matthew]

Hi, looking for information on how to integrate spell checking in the asp.net core editor component. Can anyone provide an example.  I see radspell in MVC but not core.

Thanks in advance, Matt

[Marin Bratanov]

Hello Matt,

You can find more details on spell checking a Kendo editor in the following Feedback Portal item: https://feedback.telerik.com/kendo-jquery-ui/1358507-add-spell-check-to-kendo-ui-editors.

As for RadSpell - the UI for ASP.NET AJAX controls are not supported under MVC (link), yet if you wish you could try using the RadEditor that uses RadSpell internally and review this KB article on excluding the handlers from routing. Note that should you try this, you'd need a WebForm (perhaps in an iframe in a view) and that can make things too complex, in addition to being a scenario that is not supported.

Regards,
Marin Bratanov
Progress Telerik

[Matthew]

Thanks for the response - appreciated.

I'm a little disappointed that Telerik clearly have the code needed to do spell checking yet have not implemented it in their modern .net razor core offering.  I'm sure you have a lot on but the post you refer to shows that 3rd parties can achieve it and that it was requested 4 years ago.  Dare I ask if its on a road-map?

Leaves me looking for yet another work around (that is supported).  Note my spell check was turned off (no idea why) but some users won't realise Chrome has it built in.

[Marin Bratanov]

Hello Matthew,

To be blunt and get this out of the way like a band-aid - we do not plan on implementing our own spell checking for Kendo UI. This is why its status in the feedback portal is "declined".

Here is a list of some of the reasons:

• In this day and age, browsers have spell checking turned on by default, and that is usually tied to the language they are actually using, so that takes off that configuration off your hands.
• RadSpell was implemented 16 years ago when IE6 was considered the norm and spell checking didn't exist. This is no longer the case.
• There are now many other solutions that offer spell checking and have that as their primary goal - some of them integrate explicitly with Kendo, others are browser extensions that hook on every editable field on the page. They are likely to be better and more focused on this than we could be, since we also have to maintain 100+ other components across a plethora of frameworks.
• Kendo is platform agnostic by nature. The UI for ASP.NET Core is just wrappers that, basically, generate scripts to initialize the jQuery widgets. This means that spell checking must work purely in the browser, as opposed to a .NET solution running on a server that we have in WebForms. Thus, we can't port this code, we have to rewrite everything from scratch, and even then it will come at a huge performance cost - both the size of the dictionaries, and iterating over them with JS. This does not even begin to consider custom dictionaries and their persistence. Considering the points above, this was deemed as not feasible a while ago. Doing that would mean that we don't do other things that have significantly larger impact on our customers.

I hope this explains the situation in sufficient detail.

Regards,
Marin Bratanov
Progress Telerik