Support of as you type mode for editors based on a custom data model. WProofreader fully supports ‘as you type’ mode in a wide range of WYSIWYG editors with a custom data model and virtual DOM such as CKEditor5, Quill, Trix, ProseMirror, Scribe.
Accessibility compliance updates. The green color that was used for check-boxes and radio-buttons in the Options and Languages settings tabs has been replaced with the contrast one. This is required to by WCAG 2.1 and Section 508 accessibility standards.
Enabled compound words checking in Dutch. Enabled <SplitWords> option that allows receiving correct suggestions (as a compound word, or two words separately) to words specific for the Dutch language.
Added support of SSL certificates with passwords.SSL certificates are used to setup a secure HTTP connection between the client’s application and WebSpellChecker AppServer. Since some of the SSL certificates are protected with passwords, a new parameter has been added to the AppServerX.xml file.
[WP-1810] AppServer: The following parameters doesn’t work: ‘IgnoreAllCapsWord’, ‘IgnoreDomainNames’, ‘IgnoreHtmlMarkups’, ‘IgnoreMixedCase’, ‘IgnoreMixedDigits’, ‘IgnoreNonAlphaWord’.
[WP-2380] WProofreader: Focused state is missing when using keyboard navigation between Options, Languages, Dictionary, About tabs.
[WP-2421] WProofreader: Incorrect area-label name for the opened state of the WProofreader Dialog icon.
[WP-2442] WProofreader: Incompatibility of WProofreader with Froala Editor. Incorrect behavior of getFocusableElements in component.js in place with querySelectorAll and passed array (convert array to string).
[WP-2420] Personal User Dictionary: After removing a dictionary, the words are not underlined and considered as incorrect.
1.1. Compliance with International Web Accessibility Standards (WCAG 2.1) & Keyboard Navigation
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.
1.2. Additional Notifications and Progress Indicators
Spinner. Spinner on the dialog panel that is aimed indicating the progress of proofreading. Once the proofreading process is completed, the spinner will disappear.
Save changes. We added an extra notification, warning you from leaving the dialog with changes unsaved (without clicking ‘Finish Checking’). This is made to prevent accidental loss of your proofreading results.
2. Grammar engine is updated for 8 languages
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.
[WP-2384] WSC Proofreader: elements of Proofreader are saved to DB of WordPress&Other systems and after saving are displayed on front-end.
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.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.
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.
On the technical side the Proofreader is all about minimizing the manual integration work:
A single script for all fields. Whichever types of editable fields you have in your app, there’s just a single Proofreader script, to enable spell- and grammar checking in all of them at once. Even in CKEditor5, which is currently lacking of the built-in way to proofread.
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.
Self-sustaining proofreading. Whenever you need to add new editable fields in your app, the Auto-search functionality of the new Proofreader will detect them and enable the proofreading automatically.
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:
The suggestion box is simplified. We’ve hidden rarely-used toggles and switches leaving only the primary task of choosing the correct words in the plain site.
Hover for suggestions. No clicking necessary. Spelling and grammar suggestions for marked words appear on mouseover. A subtle tactile change, making proofreading feel even more effortless.
Tuning up became easier. All the necessary settings are now always at hand under the neat badge in the bottom right corner.
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.
2. New API Options for ‘autoSeach’
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.
You can disable Proofreader in any type of editable field by class, id, data attribute and elements.
4. Trusted and Secure Installation Packages of WebSpellChecker Server
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.
1.1. WebSpellChecker Server 5.1.0 supports LanguageTool 4.2. 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: Dutch, English, German, Greek, Portuguese, Spanish, French.
1.2. Now the new grammar engine supports Java Runtime Environment (JRE) and Java Development Kit (JDK) with Java 8 and higher. Visit WebSpellChecker System Requirements to learn about the additional software and infrastructure you will need to run WebSpellChecker Server.
2. WebSpellChecker Proofreader (autoSearch)
We keep improving our new product, WebSpellChecker Proofreader, that has been introduced in one of our recent releases. Let us remind that WebSpellChecker Proofreader is based on SpellCheckAsYouType (SCAYT) core. It is designed to simplify the integration and combine the functionality of proofread as you type functionality and proofread in a dialog.
Our paid customers can already start using the first versions of WebSpellChecker Proofreader at no additional fee.
Easy to get started. A single script for all editable fields in a web app;
Auto-search functionality which detects editable fields on a web page and enables proofreading functionality;
Proofread as you type functionality on multiply languages. Spell checking functionality is supported for 16 default languages and 152 additional languages, grammar checking functionality is available for 14 out of 16 default languages.
Simplified box with corrections for spelling and grammar problems.
A new badge button with the WebSpellChecker Proofreader settings.
Supported in all modern browsers such as Chrome, Firefox, Internet Explorer 11+, MS Edge, and Safari;
Next release 5.2.0 introduces the next major updates in WebSpellChecker Proofreader:
Modern and user-friendly interface;
Combined proofread as you type and proofread in a dialog functionalities;
No need in the right mouse click to see corrections for spelling and grammar problems. Now users just hover underlined word or phrase to see open a box with corrections for spelling or grammar problem.
Please visit a demo page of WebSpellChecker Proofreader to evaluate its work. This version with proofreading in a dialog functionality will be available in our upcoming release 5.2.0 (Mid of September 2018).
[WP-2074]: Italian language spell checking: Incorrect type of the accent is used for words with final ‘e’, e.g. the Italian word for “why” is “perché“ and not “perchè”.
[WP-1964]: Overflowed local storage: Setting the value ‘scayt_0_-161398259’ exceed the quota GitHub #159: SCAYT plugin for CKEditor: SCAYT polluting global page styles.
[WP-2027]: Linux Installer: Installing WSC App on Apache Tomcat: Outdated link to the guide with the configuration of Java Application Servers.
[WP-2030]: ‘Status’ command: Incorrect description of ‘NOT ACTIVE’ status is used for the Grammar engine for WebSpellChecker Server installed on a Linux server.
[WP-1639]: Incorrect information is recorded into log files when AppServerX service is being stopped, it says that it is started instead.
[WP-2029]: AppServerX service is stopping too slow on Windows servers.
With release 5.0.1 we are introducing grammar support for 14 languages from the default languages list. Grammar feature is now supported for: English (American), English (Canadian), English (British), Danish, Dutch, French (Canadian), French, German, Greek, Italian, Portuguese, Portuguese (Brazilian), Spanish, Swedish.
Grammar is NOT supported for Norwegian Bokmal and Finnish.
This feature will be available for the customers who subscribed to Cloud Paid Services or obtained WebSpellChecker Server Licenses. The users of the Free version can use basic grammar checking functionality only for American and British English.
2. New Application Source URL in SCAYT plugin for CKEditor
We have combined bunch of separate applications which used for various integrations with rich text editors and plain HTML editable elements into a single unified bundle application. Now we have a single backward compatible application JS file (wscbundle.js) that can be used instead for all these integrations.
Default path to SCAYT plugin for CKEditor has been changed from …/ckscayt.js to …/wscbundle/wscbundle.js.
The old path to …/ckscayt.js is backward compatible and keep working as before.
3. User Interface Updates in SCAYT plugin for CKEditor
3.1. Languages Tab
We have removed green marks and legend related to grammar supported languages. At the moment there are not marks as now grammar is supported almost for all the languages in the list.
4. User Manuals Updates
4.1. SCAYT plugin for CKEditor User Manual
We have made several minor updates in User Manual to outline changes related to the introducing the extended grammar support. The view of the Language tab and add description about supported languages for grammar functionality.
4.2. WebSpellChecker Proofreader User Manual
We have updated the description of the Language tab section by adding a note about the introducing the extended grammar support for 14 languages from the default languages list. Visit WebSpellChecker Proofreader User Manual 5.0.1.
5. Enlarged Medical Dictionary
Each year modern technologies and researchers in the medical field boost the number of new medical terms that come into use. Our team is keeping an eye on this evolving trend and trying to maintain the Medical word list up-to-date. This time our English Medical Dictionary has been extended with more than 1,600 new medical terms.
GitHub #2882: SCAYT plugin for Froala Editor: Spell checker crashes if .fr-box gets hidden
[WP-1548] – SCAYT & WSC plugin for CKEditor: WSC JS error in console “Cannot read property ‘split’ of undefined”
[WP-1833] – SCAYT plugin CKEditor: Markup is not set for a specific case in IE10
[WP-1769] – SCAYT plugin for CKEditor: Accessibility issue: No alt tag for Logo image on About tab
[WP-1947] – SCAYT for Editable Controls: SCAYT with declarative initialization can’t be disabled
[WP-478] – SCAYT for Editable Controls: Focus is jumping after Disable SCAYT in FF/IE11
[WP-1884] – SCAYT plugin for TinyMCE: There is an error “Failed to load resource: the server responded with a status of 404 (Not Found) tinymce.woff”
[WP-1865] – WSC plugin for TinyMCE: Incorrect title “wsc_button_desc” is used for the ABC button
[WP-1897] – WSC for Editable Controls: WSC dialog/modal window is not loaded properly when a custom virtual directory used for initialization instead of default /spellcheck
[WP-1837] – Web API: The format (XML/JSON) parameter doesn’t work for “get_lang_list” command
[WP-1431] – User Dictionary: Incorrect dictionary name is recorded log files and adding extra prefix ud_ud_1000000