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.
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 administrativeStatus / " normative status" of a term
The following mappings are hard-coded in the import process
Term status in translate5 | Mapped TBX status |
---|---|
Preferred term | preferredTerm proposed |
Normal term | admittedTerm And all TBX term status, that are not listed. |
Deprecated/Forbidden term | deprecatedTerm supersededTerm deprecated |