This is a hot fix release for the issue discovered in WProofreader when working with right to left languages.
A new virtual mechanism has been introduced for processing and underlying spelling and grammar errors in the wide range of the editable fields (HTML editable elements, and classic rich text editors such as CKEditor 4, Froala Editor, TinyMCE, etc.). With such an approach WProofreader creates a separate virtual layer behind the original element, and doesn’t affect the original content.
Previously, it added extra span elements with styles to wrap incorrect words and phrases. In certain cases those extra elements were saved to a database which resulted in the text pollution with unwanted text unless those elements are cleaned with the additional function. The new mechanism eliminates those issues.
<script>
window.WEBSPELLCHECKER_CONFIG = {
autoSearch: true,
enableGrammar: true,
...
onLoad: function(instance) {
var element = instance.getContainerNode();
element.instance = instance;
}
};
</script>Visit the updated license activation guides for more details.
{
"Spell Check Engine": {
"active": true
},
"Grammar Check Engine": {
"active": true
},
"Thesaurus Engine": {
"active": true
}
}<SSLCertificatePassword></SSLCertificatePassword>Please visit Configuring WebSpellChecker Server Parameters to find all available parameters in AppServerX.xml. In Setup SSL Connection with AppServer 5.0, you will find the guidance how to secure your requests.
1.1. Added new options for WProofreader management. Two new API options enableAutoSearchIn and disableAutoSearchIn are added to give more control over the autoSearch functionality.
<script>
window.WEBSPELLCHECKER_CONFIG = {
...
enableAutoSearchIn: ['.class', '#id', '[data-attribute]', 'textarea'],
...
}
</script><script>
window.WEBSPELLCHECKER_CONFIG = {
...
disableAutoSearchIn: ['.class', '#id', '[data-attribute]', 'textarea'],
...
}
</script>1.2. API documentation updates. API documentation is updated with the descriptions of the following parameters: autoSearch, enableAutoSearchIn, disableAutoSearchIn.
enableAutoSearchInInputs option is no longer supported as it was replaced by enableAutoSearchIn.
1. Added better descriptions of errors for the cases of incorrect use of the cmd parameter.
With this update in WebSpellChecker Proofreader 1.2, we have introduced a bunch of updates to meet the requirements of the international web accessibility standards from W3C Web Accessibility Initiative (WAI). Specifically, we relied on the Web Content Accessibility Guidelines (WCAG), including WCAG 2.0 and WCAG 2.1.
Visit WSC Proofreader Keyboard Navigation to learn more about the keyboard navigation in WSC Proofreader.
WebSpellChecker Server 5.2.2 supports LanguageTool 4.3. We have upgraded the version of the new 3rd party grammar engine, LanguageTool, that was integrated into WebSpellChecker as a part of our major release 5.0.0.
As a part of this upgrade new and improved grammar rules for the next languages: Catalan, Dutch, American and British English, French, German, Portuguese, Russian, and Ukrainian.
With the release 5.2.2 we stopped support of old plugins and list of the integrations that were based on the older products.
SCAYT plugin for TinyMCE 4
WSC Dialog plugin for TinyMCE 4
WSC Dialog for HTML Editable Controls
However, instead we are offering much better and flexible integration with WProofreader. It can be easily integrated with almost any WYSIWYG editor, including classic HTML editable elements.
1.1. ‘Maximize/Restore’ button in a dialog mode.
1.2. Improved notifications on the UI when working with user dictionary to bring clarity to your users. Check our video to learn more about notifications and how to use personal user dictionary with WebSpellChecker Proofreader.
The grammar checking for Ukrainian, Russian, Catalan, and Swiss German languages is now available in both Server and Cloud versions.
While providing you with the proofreading tools and services, we gradually implemented your suggestions on making the spell- and grammar checking more convenient. Still, there’s a limit of brushing up the old products. To make the tangible change, we decided to create a whole new solution, based on your and other customers’ ideas on how proofreading should be done in the modern Web. Today we are happy to introduce you the all-new Proofreader. We hope it will become just what your users and your development team lacked for their spell- and grammar checking needs.
The Change: All Proofreading Modes in One Place
From now on you don’t have to sacrifice one usage scenario in favor of the other. The Proofreader comprises the proofreading modes, which were previously available only in separate products. Now your app’s users can decide how they want their text proofread: be it correcting mistakes as they type, or hasteless proofreading of all the text at once in a separate dialog.
Installed Instantly
On the technical side the Proofreader is all about minimizing the manual integration work:
Here is a list of rich text editors and editors based on custom model where we have a chance to test our Proofreader: CKEditor 4.0+, CKEditor 5, Froala Editor, TinyMCE 4.0+, Kendo UI, Textbox.io, Summernote, Nicedit, Redactor, Quill, Trix, ProseMirror, Draft.js, Scribe.
There is wide list of other editors available, we haven’t test it everywhere. If you have an editor that is outside this list, it doesn’t mean that Proofreader won’t work there. We encourage you to try first and see if it works. In case you experience any troubles with the integration, reach us, and we will try to help.
Please visit Get Started with Server WSC Proofreader (autoSearch) and Get Started with Cloud WebSpellChecker Proofreader (autoSearch) for guidance accordingly.
Looks Fresh, Feels Smooth
Somehow it feels better to work with good-looking tools. Just remember how jotting the first words in a new crispy notebook feels. When designing the new Proofreader we wanted to make checking spelling and grammar clean and comfortable, thus making it play for your app’s overall interaction experience. Here are the core UI changes:
Simple, but Not Plain
As easy as it looks the Proofreader is powered by the mighty WebSpellChecker proofreading engine, providing spell checking in 16 default and 152 additional languages, and grammar checking in 14 out of 16 default languages in all modern browsers.
We added two new API options that give more control over the autoSearch functionality of WebSpellChecker Proofreader. By default, Proofreader with the enabled ‘autoSearch’ option will be enabled in all supported editable fields on the page. However, we understand that this might be inconvenient, as there might not be a need to check some types of editable fields. Now you can choose where you want disable Proofreader.
disableAutoSearchIn
You can disable Proofreader in any type of editable field by class, id, data attribute and elements.
disableAutoSearchIn: ['.class', '#id', '[data-attribute]', 'textarea'],enableAutoSearchInInputs
We decided to disable Proofreader auto-enabling in the HTML <input> element by default. However, you may change this behavior and allow Proofreader checking in <input>.
enableAutoSearchInInputs: true,We enlarged both American and British Medical dictionaries with 550 new terms. Visit a demo page with Medical dictionary to evaluate its quality.
With WebSpellChecker Server 5.2.0, we improved the security of our installation packages for Windows servers. Now our builds are more secure as signed using a code signing certificate issued by a trusted Certificate Authority. It gives an additional warranty for our customers that our software can be trusted, and it doesn’t come from a malicious hacker.