Re: [w3c/editing] spellchecking - how to give JS devs more control (#166)

> > The size of that package is around 160MB for a set of mot major languages. Maybe in 10 years time that is something we can just embed in a webpage, but for now it still needs to be done server side.

> Totally agree. Today (and I think that won't change) this should be done on the server side. But that itself doesn't change the picture of what happens on the client. It just happens slower.

I think there two uses cases:
- when the editor (like @erickponce's company) want to include some check in the web page. In that case I partially disagree with you because the editor can know the language used. So only one or two languages are downloaded, And only one time if the browser web cache is used.
- when someone (a company or a free project) want to create a browser extension. In that case I totally disagree with you because all dictionaries and check rules can be stored on client side and the extension can load them when it's needed. 

> However, server-based spell checking doesn't always make sense. Some pages may need to work while offline. And it doesn't really make sense to spend a lot of server resources on something that the browser can do already given that browsers OSes come bundled with spellcheckers.

I agree with you but I want to include another difference:
- Level 1: spell check: check if some ~wor**r**d~ word exist in a ~diction**n**ary~ dictionary.
- Level 2: grammar/syntax check: check if all ~word~ word**s** ~create**s**~ create a sentence without any ~error~ error**s**.
- Level 3: semantics check: check if there no ~bugs~ **errors** in the sentence.

Notes:
- Browsers perform only spell check, few addons/web-service perform grammar check but no-one perform semantics check.
- Each checker may also include few statics "find and replace" rules to perform few checks on very common errors from above levels.
- Each checker also check for below levels.

For info there a French open-source grammar checker ([grammalecte](https://grammalecte.net)) that perform Both spell AND grammar check on client side. The grammar checker runs in a Worker launched from the background script. (But only check french)

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/editing/issues/166#issuecomment-683421008