The TBX file must follow the TBX core standard.
Importing TBX files, which claim to be TBX, but do not follow TBX core standard, may not work on import (files like SDL Multiterm or Across may export).
Please note: translate5 project strives to support the proprietary TBX derivatives or other proprietary text based terminology formats. Any kind of support for this development is welcomed.
More information about how terminology data from TBX files is used in translate5.
Which terms translate5 uses for a task
translate5 evaluates the language identifiers of the task (source and target languages) and of the TBX file.
It behaves in the way of the following examples
| Language identifier in TBX | Language identifier in source or target language in translate5 task | Terms get marked in corresponding language in translate5 |
|---|---|---|
| en | en | YES |
| en | en-US | YES |
| en-US | en | YES |
| en-US | en-GB | NO |
Mapping of TBX "administrativeStatus" / "normative status" of a term
The following mappings are predefined in translate5 and are used in the import process.
The mappings can be changed via configuration. See below.
| Term status in translate5 | Mapped well known TBX status |
|---|---|
| Standardized term | standardizedTerm |
| Preferred term | preferredTerm preferred |
| Normal term | admittedTerm And all other TBX term status, that are not listed or configured. |
| Deprecated/Forbidden term | deprecatedTerm Additionally the following non standard values are defined as forbidden in the configuration: <termNote type="across_ISO_picklist_Usage">do not use</termNote> |
Depending of the tbx structure (not standard tbx) of your third party application you can search the non standard content and replace the usage status as follows:
| Wanted usage status | Replace with |
|---|---|
| Standardized | <termNote type="administrativeStatus">standardizedTerm-admn-sts</termNote> |
| Preferred | <termNote type="administrativeStatus">preferredTerm-admn-sts</termNote> |
| Normal/Others | <termNote type="administrativeStatus">legalTerm-admn-sts</termNote> |
| Admitted | <termNote type="administrativeStatus">admittedTerm-admn-sts</termNote> |
| Deprecated/Forbidden | <termNote type="administrativeStatus">supersededTerm-admn-sts</termNote> |
Term status configuration
Mapping of term statuses to translate5 statuses
In the configuration the well known TBX statuses are mapped to the translate5 statuses:
runtimeOptions.tbx.termLabelMap.supersededTerm = forbidden runtimeOptions.tbx.termLabelMap.preferredTerm = preferred
And so on. This mappings can be changed if needed.
Mapping of unknown statuses
Additionally to the well known statuses other statuses can be added to translate5 by adding configuration values, the following are predefined in the configuration:
runtimeOptions.tbx.termImportMap.across_ISO_picklist_Usage.do not use = supersededTerm runtimeOptions.tbx.termImportMap.across_ISO_picklist_Verwendung.Unwort= supersededTerm runtimeOptions.tbx.termImportMap.across_userdef_picklist_Verwendung.Unwort = supersededTerm
The relation of the configuration value is always to a TBX termNote element. The name convention is: the fourth part of the configuration name (example: across_ISO_picklist_Usage) is compared to the termNote type Attribute.
The fifth part "do not use" is compared with the tag content. This would match the following termNote tag: <termNote type="across_ISO_picklist_Usage">do not use</termNote>
If a term has such a matching termNote tag, the configured status (here in the example "supersededTerm") is used then.
Default value of unknown status
If a term has an unknown status the default status is used. This is "admittedTerm" by default and can be changed in the configuration variable named "runtimeOptions.tbx.defaultTermStatus".
If the term has no status at all, the default status will be used too. If the term as a no status or an unknown status a log entry is generated.