How to enable spellchecking in user forms

PRPC 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.

Spellchecking is available only for user forms based on harnesses that use the SmartFrames form of the Layout tab and include the spellchecker icon.

To include the spellcheck capability in a user form:

1. Open the harness
2. Click the down arrow () in the Basic control group () and select the Icon control (). Drag the Icon control to the cell or header area that is to contain it. When the pointer changes shape to indicate that a single cell or header is selected, release the mouse button.
3. Click () to display the Cell Properties panel. PROJ-649 5.4
4. Complete the Cell Properties panel. Select Spell Checker as the Type. The corresponding icon appears on the form (). See Harnesses, Sections, and Flow Actions — Adding an Icon.
5. Save the Harness form.
6. Test.

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.)

By default, spellchecking is enabled for input fields that reference Text Area (pxTextArea) and disabled for Text Input (pxTextInput) auto-generated control rules. This functionality cannot be modified.

Non-auto-generated controls

By default, spellchecking is enabled in the non-auto-generated control rule TextArea that produces an HTML tag of the form:

<INPUT TYPE="TEXTAREA" ... >

To disable spellchecking for a property that is represented with a TEXTAREA tag:

1. Open the property.
2. Open the control rule referenced in the property.
3. Copy and save the control rule into an application RuleSet, changing the name.
4. Click() to edit the HTML text of the copy. Add the HTML attribute SPELLCHECKENABLED="false" to each <TEXTAREA> tag. MELLJ 6/13/06 B-21342 added D
5. Save the new control rule.
6. Update the property to reference the new control rule.

By default, spellchecking is disabled in the non-auto-generated control rule Text that produce an HTML tag of the form:

<INPUT TYPE="TEXT" ... >

To enable spellchecking for a property that is represented with a TEXT tag:

1. Open the property.
2. Open the control rule referenced in the property.
3. Copy and save the control rule into an application RuleSet, changing the name.
4. Clickto edit the HTML text of the copy. Add the HTML attribute SPELLCHECKENABLED="true" to each <INPUT TYPE="TEXT" > tag.B-21342
5. Save the new control rule.
6. Update the property to reference the new control rule.

When the spellcheck icon is visible at runtime, any user who can update the work item 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).