Date: Fri, 29 Mar 2024 08:32:18 +0200 (EET) Message-ID: <59452593.652.1711693938225@ip-172-30-3-56.ec2.internal> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_651_407969879.1711693938218" ------=_Part_651_407969879.1711693938218 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
With release v5.7.0, we intro= duced an enhanced AI-based proofreading engine for English. It was built us= ing modern approaches in Natural Language Processing (NLP). Unlike the clas= sical rules or dictionary-based engines, it's based on the huge pre-trained= language model. Its accuracy is at least three times better.
However, at the same time, there are = some cons that should be taken into consideration:<= /p>
You can give it a try using one of th= e public demos on our website: https://webspell= checker.com/wsc-proofreader/
If you are using the server-based pac= kage of WebSpellChecker v5.7.0 and higher, then you have an AI engine inclu= ded in the package.
<Language Id=3D= "en_AI"> <Alias>ai</Alias> <GrammarCheckProvider>neural</GrammarCheckProvider> <GrammarCheckProviderOptions>en</GrammarCheckProviderOptions&g= t; <!--<ThesaurusEnabled>true</ThesaurusEnabled> <SpellEngineOptions> <Locale>am</Locale> <SpellCheckProvider>ssce</SpellCheckProvider> <Dictionary FullPath=3D"ssceam2.clx" > <ForSuggest>no</ForSuggest> </Dictionary> <Dictionary FullPath=3D"ssceam2s.clx"> <ForSuggest>yes</ForSuggest> </Dictionary> <Dictionary FullPath=3D"keywords.clx"></Dictionary> <Dictionary FullPath=3D"ssceam.tlx"></Dictionary> </SpellEngineOptions>--> </Language>
You can enable an AI-based engine and= use it as a grammar provider for one of the existing dialects, e.g. Americ= an English.
1. Stop AppServer before making any c= hanges in AppServerX.xml.
2. Go to AppServerX.xml file and open= it for editing.
3. Scroll down to the section with la= nguage tags. Locate the language tag <Language Id=3D"en_US">...</L= anguage> for American English.
The same approach can be used for any= other available dialects of English, e.g. British or Canadian English.
<Language Id=3D= "en_US"> <Alias>en</Alias> <Alias>am</Alias> <GrammarCheckProviderOptions>en-US</GrammarCheckProviderOption= s> <ThesaurusEnabled>true</ThesaurusEnabled> <SpellEngineOptions> <Locale>am</Locale> <SpellCheckProvider>ssce</SpellCheckProvider> <Dictionary FullPath=3D"ssceam2.clx"> <ForSuggest>no</ForSuggest> </Dictionary> <Dictionary FullPath=3D"ssceam2s.clx"> <ForSuggest>yes</ForSuggest> </Dictionary> <Dictionary FullPath=3D"sscema2.clx"/> <Dictionary FullPath=3D"keywords.clx"/> <Dictionary FullPath=3D"ssceam.tlx"/> </SpellEngineOptions> </Language>
4. Add an extra tag, <= ;GrammarCheckProvider>neural</GrammarCheckProvider>, = ;inside the language tag. The value should be neural.
<Language Id=3D= "en_US"> ... <GrammarCheckProviderOptions>en-US</GrammarCheckProviderOption= s> <-- Enabling AI-based engine as a grammar check provider. --> <GrammarCheckProvider>neural</GrammarCheckProvider> ... </Language>
5. Fix the default value inside = <GrammarCheckProviderOptions>...</GrammarCheckProviderOpti= ons> from en-US to en.= span>
<Language Id=3D= "en_US"> ... <GrammarCheckProviderOptions>en</GrammarCheckProviderOptions&g= t; <-- Enabling AI-based engine as a grammar check provider. --> <GrammarCheckProvider>neural</GrammarCheckProvider> ... </Language>
6. Start AppServer to apply changes.<= /span>
There is an option that also allows u= sing two grammar checking engines at the same time. Though one engine sugge= stion will take precedence over the other.
Again, all the changes should be made= in the AppServerX.xml file.
1. Stop AppServer before making any c= hanges in AppServerX.xml.
2. Go to AppServerX.xml file and open= it for editing.
3. Locate <=
;GrammarCheckEngine>...</GrammarCheckEngine=
> tag. Inside this tag you will find
<GrammarCheckEn= gine> <!-- The grammar provider, can be one of langtool (default), atd, ne= ural, mixed. --> <GrammarCheckProvider>mixed</GrammarCheckProvider> ... </GrammarCheckEngine>
4. Uncomment <MixedProvider>...</MixedProvider>=
and inside <Providers>...</Providers>, specify neural,langtool separated by comma.=
p>
5. Now you can apply the mixed approa=
uch with the grammar engines to one of the languages. Let's try to enable the mixed=
engines for American English. for Scroll down to the section with=
language tags. Locate the language tag <Language Id=3D"en_US">...<=
;/Language> for American English. 6. Add an extra tag, <GrammarCheckEn=
gine>
<!-- The grammar provider, can be one of langtool (default), atd, ne=
ural, mixed. -->
<GrammarCheckProvider>mixed</GrammarCheckProvider>
<MixedProvider>
<Providers>neural,langtool</Providers>
<!-- <CustomPrioritiesFile>CustomPriorities.xml</Custom=
PrioritiesFile> -->
</MixedProvider>
...
</GrammarCheckEngine>
<Language Id=3D= "en_US"> ... <GrammarCheckProviderOptions>en-US</GrammarCheckProviderOption= s> <-- Enabling a few engines as grammar check providers. --> <GrammarCheckProvider>mixed</GrammarCheckProvider> ... </Language>
7. Fix the default value inside&= nbsp;<GrammarCheckProviderOptions>...</GrammarCheckProvide= rOptions> from en-US to en.
<Language Id=3D= "en_US"> ... <GrammarCheckProviderOptions>en</GrammarCheckProviderOptions&g= t; <-- Enabling a few engines as grammar check providers. --> <GrammarCheckProvider>mixed</GrammarCheckProvider> ... </Language>
8. Save changes in AppServerX.xml fil= e and start AppServer.
Now you will have the results generat= ed by two engines as green underlines.