Please have a look at the “Spell Checker (simple)” node for a general description of the spell checking and correction mechanism and the supported languages.
This node creates spelling correction rules. For each potential error in the given text, a new row with a so called “rule match” is created. The rule match points to the corresponding text fragment, contains several replacement suggestions and an identifier and description of the specific rule.
The structure of the created rule table looks as follows:
|Input Row ID||The Row ID of the input text.|
|From Position||The rule’s start offset in characters in the input text.|
|To Position||The rule’s end offset in characters in the input text.|
|Value||The original, uncorrected value in the input text.|
|Suggested Replacements||A list of potential replacement suggestions.|
|Rule ID||Identifier of the rule.|
|Message||Human-readable message of the rule.|
You can use standard KNIME nodes (e.g. “Row Filter”) to manipulate the list of rules before applying them with the “Spell Checker: Apply Rules” node.
You want to see the source code for this node? Click the following button and we’ll use our super-powers to find it for you.
A zipped version of the software site can be downloaded here.
Deploy, schedule, execute, and monitor your KNIME workflows locally, in the cloud or on-premises – with our brand new NodePit Runner.Try NodePit Runner!
Do you have feedback, questions, comments about NodePit, want to support this platform, or want your own nodes or workflows listed here as well? Do you think, the search results could be improved or something is missing? Then please get in touch! Alternatively, you can send us an email to firstname.lastname@example.org, follow @NodePit on Twitter, or chat on Gitter!
Please note that this is only about NodePit. We do not provide general support for KNIME — please use the KNIME forums instead.