The "language style" structure of the entries in the input tables is accomplished using special dictionary files associated with either standard or customized (or both) input files. These dictionary files are required to translate data elements to the TS Quality standard.
Regardless of the data being processed (customer or business), these dictionary files are required if any parts of the input definitions match these conditions:
- in a foreign language, or
- do not use only TS Quality standard names (is non-standard)
The encoding of the dictionary is the same as the corresponding input file’s encoding.
What dictionary files look like
Dictionary files contain keywords paired together ( TS Quality standard, User Choice). The keywords are always separated by commas:
Like this: |
Standard, User choice (for translations) Note: User choice must NOT be
null.
|
Or this: |
Standard, Standard (for words that require no translations) |
The user must define all TS Quality standard elements used in the input definition file. Every keyword and attribute used in the input definitions file must have a corresponding pair in the dictionary (even if no translation is needed for a certain word). The elements in the input table have to be "translated".
Assume your customized definitions table is in Spanish. A dictionary file is required because you are processing data in a foreign language. The name of the dictionary has to be specified for the associated input definitions table using the Parser Tuner .
If your file has these entries:
The dictionary file must have at least the following entries:
Special Notes on Dictionary Files
Please note the following issues when creating dictionary files: