Customization of the rules

All terms (1-word and multi-word) are unknown to the term checker until they are specified in the disambiguation files. If you do not add your organization's technical names and the technical verbs to the term checker, the term checker cannot fully analyze your text.

For help with writing the rules, refer to Use an XML editor or a text editor that has syntax highlighting (

To buy customization services, contact TechScribe.

To customize the term checker

  1. Add technical names and technical verbs to disambiguation-projectterms.xml.
  2. Add unapproved terms and misused terms to grammar-projectterms.xml.
  3. By default, the term checker identifies some capitalized text as a proper noun. Thus, the term checker does not give a warning for some misused text. (The text conforms to ASD-STE100, but the technical name is not correct.) To prevent this problem, in grammar-ste7.xml, change rule 1.1 so that it does not ignore proper nouns.
  4. To make sure that the rules are correct, use 'testrules' ( If you put a technical term that contains an STE approved term or a not-approved term into disambiguation-projectterms.xml, you can cause 'testrules' to give an error message. To prevent the error message, in disambiguation-ste7.xml, change the applicable example or put the example into comments. (With the evaluation version of the term checker, you cannot change disambiguation-ste7.xml, because it is on the TechScribe website.)

Add terms to disambiguation-projectterms.xml

The term checker contains technical names from these sources:

The term checker contains many technical verbs that are in rule 1.12.

For each approved term that is not in the term checker, add each inflection of the term. Use the rules that are in disambiguation-projectterms.xml as templates. If a term is approved for only 1 meaning, and if you want to give guidelines to technical writers, then add a grammar rule for that term.

The term checker finds all unknown terms, but not proper nouns. Thus, rules for unapproved terms are not necessary. But, to give guidelines to technical writers, do these:

  1. Add an unapproved term in disambiguation-projectterms.xml. If you do not add the unapproved term, then the term checker will give 2 warnings for the unapproved term. One warning will be 'unknown term' and the other warning will be the warning from the rule that you write in grammar-projectterms.xml.
  2. Add the unapproved term in grammar-projectterms.xml.

Simplify noun clusters (part of rule 2.2)

To simplify a noun cluster, you can "use hyphens (-) between words that are used as a single unit." Sometimes, hyphens in different locations are possible. For example, for the noun cluster filter unit top cover, hyphens in these locations are possible:

Add terms to grammar-projectterms.xml

To give guidelines to technical writers, add terms to grammar-projectterms.xml. Typically, add rules for these:

Sometimes, a 1-word approved project term is an unapproved STE term. For example, for software documentation, the term render is a technical verb. The rule in grammar-ste7.xml will give correct results because of the exception. But, 'testrules' will give an error message. To prevent the error message, put the rule into comments or delete the rule from grammar-ste7.xml. Optionally, add a rule in grammar-projectterms.xml to tell technical writers to use the term only with its approved meaning.

Change grammar-ste7.xml rule STE_RULE_1_1_USE_APPROVED_WORDS so that it does not ignore proper nouns

In LanguageTool, proper nouns have the postag NNP. Examples: London, Saudi Arabia, Tuesday, September, HTML, John Smith.

The term checker has rules that identify capitalized text as a proper noun. The term checker gives these proper nouns the postag IS_NNP. To prevent the term checker from using these rules, in grammar-ste7.xml rule STE_RULE_1_1_USE_APPROVED_WORDS, put this exception into comments:

            <exception postag="IS_NNP"/><!-- Proper nouns are from disambiguation rulegroup STE_TN_NOUN-PROPER. -->

Other customization

You can customize the rules to make other types of language quality-assurance software such as these:

RSS feed