Show all
Six configuration elements work
together to provide users the ability to check spelling in work
object forms:
- Fixed dictionaries in a compressed format, stored in
binary file rules
- Supplemental dictionaries in text file rules
- Settings in a Spellchecker Properties data instance for a
locale
- HTML property rules associated with text properties to be
checked
- Harness rules (SmartFrames layout) that contain the
Spellcheck icon ()
- User locale and privilege settings
When enabled and activated by a user, spellchecking by
default checks the spelling in all input text fields on a work
object form (corresponding to the HTML code <INPUT TYPE=TEXT
> and specially configured text boxes (that have <INPUT
TYPE=TEXTAREA >.
1. Set
up dictionaries
Process Commander includes dictionaries that support three
English locales and two other languages:
en-US
locale — United States
English
en-CA
locale — Canadian English
en-GB
locale — British English
fr
locale — French (France)
de
locale — German (pre- and
post-Reformation)
For any of these locales, you can add one or more
supplemental dictionaries with additional terms specific to
your company or application. A supplemental dictionary is
stored in a text file rule, which may belong to either a
locked RuleSet version or an open RuleSet version. When the
RuleSet version for a supplemental dictionary is not locked,
users who have the appropriate privilege can add new words to
the dictionary during spellcheck operations.
To support locales other than those listed above, your
organization can acquire the dictionaries directly from
Wintertree Software. The dictionaries can be loaded into
rules in your application and configured through Spellchecker
Properties data instances.
The spellchecker software uses two forms of dictionaries,
a compressed form (CLX file type, saved as a binary file
rule) and a specially formatted text file (TLX file type,
saved as a text file rule). Each language has at least one of
each type. Supplemental dictionaries use the TLX format.
2. Set
up a SpellChecker Properties data instance
3.
Update harness rules
4.
Control which properties support spellchecking
This step is optional. By adjusting the HTML
representation of a property, you can control which
properties can be spellchecked. (Users can check spelling can
only for properties presented in read-write mode, which
allows the corrected spellings to be entered.) Spellchecking
can be enabled on properties that appear as the HTML elements
with type of TEXTAREA or TEXT elements.
By default, spellchecking is available for input fields
properties on work object forms (created from harness rules)
of three categories:
- All simple TEXT fields
- Input fields that reference one of the two standard
HTML Property rules textarea or
textareaexpanded
- Custom HTML Property rules that produce an HTML tag of
the form:
<INPUT TYPE="TEXTAREA" ...
>
TEXTAREA elements
To disable spellchecking for a property that is
represented with a TEXTAREA tag:
- Open the property rule.
- Open the HTML property rule referenced in the property
rule.
- Copy and save the HTML property rule into an
application RuleSet, changing the name.
- Click the pencil icon () to edit the HTML text of the copy.
Add the HTML attribute
SPELLCHECKENABLED="false"
to each
<TEXTAREA> tag.
- Save the new HTML property rule.
- Update the property rule to reference the new HTML
property rule.
TEXT elements
To enable spellchecking for a property that is
represented with an <INPUT TYPE=TEXT> tag:
- Open the property rule.
- Open the HTML property rule referenced in the property
rule.
- Copy and save the HTML property rule into an
application RuleSet, changing the name.
- Click the pencil icon to edit the HTML text of the
copy. Add the HTML attribute
SPELLCHECKENABLED="true"
to each
<INPUT TYPE="TEXT" >
tag.
- Save the new HTML property rule.
- Update the property rule to reference the new HTML
property rule.
5. Set
user locale and privileges
When the spellcheck icon is visible at runtime, any user
who can update the work object can perform the spellcheck.
The current locale of the user determines which SpellChecker
Properties instance applies, and so which dictionaries apply.
Users can change their locale through Windows workstation
facilities, the Locale Settings tool, or by running an
appropriate activity.
Only users who hold the privilege
@baseclass.AddtoDictionary can insert new words
into a user dictionary. Such users must also have the ability
to update rules in the RuleSet version that contains the user
dictionary (a text file rule).
User Interface category