ContentBody{} FormattedBody{value='
Fields
Some of the TBX fields can be synchronized out of the box, users also can create custom fields and map it to Memsource field types in Export Settings mapping.
TermWeb field | Memsource field |
---|---|
Term fields | |
See languages section after this table | Language |
No exact match, we can match custom field value or TBX | Status |
Usage status (TBX) – value | Preferred |
Usage note (TBX) | Usage |
Part of speech (TBX) | Part of speech |
Gender (TBX) | Gender |
No exact match, we can match custom field value or TBX | Forbidden |
No exact match, we can match custom field value or TBX | Case sensitive |
No exact match, we can match custom field value or TBX | Match type |
Usage note (TBX) | Usage |
Part of speech (TBX)
| Part of speech
|
Gender (TBX) TBX values:
| Gender
|
Grammatical number (TBX)
| Number
|
No exact match, we can map custom field value | Short translation |
Term type (TBX)
| Term type
|
Note By default Memsource adds here all fields which are not matching other fields (including concept level fields) | |
Concept fields | |
Definition (TBX) | Definition |
Custom field with ExportSettings mapping to Memsource type | Concept note |
Section | Can’t be mapped and Memsource inserts it into Term’s note |
Domains | Domain/Subdomain Not implemented. |
Custom field with ExportSettings mapping to Memsource type | URL |
Languages
Memsource supports language tags with separators as dash ‘-' and underscore '_’.
...