{"id":37886,"date":"2022-10-21T16:09:00","date_gmt":"2022-10-21T16:09:00","guid":{"rendered":"https:\/\/webspellchecker.com\/?p=37886"},"modified":"2022-10-24T16:24:49","modified_gmt":"2022-10-24T16:24:49","slug":"whats-new-at-webspellchecker-english-dialects-autocomplete-v2-custom-dictionary-api","status":"publish","type":"post","link":"https:\/\/webspellchecker.com\/blog\/2022\/10\/21\/whats-new-at-webspellchecker-english-dialects-autocomplete-v2-custom-dictionary-api\/","title":{"rendered":"What\u2019s new at WebSpellChecker: English dialects, Autocomplete v2, custom dictionary API"},"content":{"rendered":"\n
\"What\u2019s<\/figure>\n\n\n\n

Dear WebSpellChecker clients,<\/p>\n\n\n\n

Long time, no news from WebSpellChecker. It may seem that we\u2019ve slowed down the development pace. But, in fact, no. Although the war creates the most challenging conditions for business here in Ukraine<\/strong>, we have already got WebSpellChecker back on track \ud83d\ude0e.<\/p>\n\n\n\n

And even beyond \u2014 we\u2019ve developed some exciting features like AI-based English dialects, custom dictionary API, a new version of autocomplete, etc.<\/p>\n\n\n\n

Chances are you will fancy them. So, long story short, since March until today WebSpellChecker has been about\u2026<\/p>\n\n\n\n

American, British, Canadian, Australian? Take them all.<\/h2>\n\n\n\n

English dialects have always been inside our dictionary-based engine. It was time for us to add them to AI models.<\/p>\n\n\n\n

After deep linguistic research<\/a> and sophisticated implementation, now English AI is equipped with the support for unique spelling for 4 dialects \u2014 American, British, Australian, and Canadian.<\/p>\n\n\n\n

No confusion and brain-racking on how to write capitalize<\/em> or capitalise<\/em> in any dialect. English AI, enabled by default in your product, definitely knows how. <\/p>\n\n\n\n

Besides, we\u2019ve made a bunch of fixes to improve the output of English AI model. <\/p>\n\n\n\n

New autocomplete with smarter suggestions<\/h2>\n\n\n\n

Autocomplete was designed to quicken your writing<\/a>. We agree that with one-word suggestions, there may be no apparent change in texting speed.<\/p>\n\n\n\n

What about 2-word or even 3-word suggestions? Type \u201cThanks for\u201d, <\/em>and we\u2019ll offer \u201cvisiting our website\u201d.<\/em> Our autocomplete feature has become smarter and now suggests longer phrases. To enjoy faster writing, just enable autocomplete suggestions in the settings. <\/p>\n\n\n\n

Besides, we\u2019ve fixed some issues and cut the number of false or erroneous suggestions. Autocomplete improvements are to be continued. <\/p>\n\n\n\n

Custom dictionary API<\/h2>\n\n\n\n

No client request goes to oblivion. We process and record all your feature suggestions and recommendations.<\/p>\n\n\n\n

Custom dictionary API was one of such requests. Before, WebSpellChecker clients could create only user dictionaries via API. Now, we\u2019ve added a custom dictionary API option for the on-premise package<\/strong>. You can create and manage custom dictionaries, add words, filter lists, etc., using API. <\/p>\n\n\n\n

Custom dictionary API for Cloud clients is coming soon. Contact us<\/a> to get the manual.<\/p>\n\n\n\n

Ever-developing WProofreader SDK<\/h2>\n\n\n\n

With every release, we add bells and whistles to WProofreader<\/a>. This time, we updated the product UI and enhanced the behavior:<\/p>\n\n\n\n