/AWS1/CL_XL8TERMINOLOGYDATA¶
The data associated with the custom terminology. For information about the custom terminology file, see Creating a Custom Terminology.
CONSTRUCTOR¶
IMPORTING¶
Required arguments:¶
IV_FILE TYPE /AWS1/XL8TERMINOLOGYFILE /AWS1/XL8TERMINOLOGYFILE¶
The file containing the custom terminology data. Your version of the AWS SDK performs a Base64-encoding on this field before sending a request to the AWS service. Users of the SDK should not perform Base64-encoding themselves.
IV_FORMAT TYPE /AWS1/XL8TERMINOLOGYDATAFORMAT /AWS1/XL8TERMINOLOGYDATAFORMAT¶
The data format of the custom terminology.
Optional arguments:¶
IV_DIRECTIONALITY TYPE /AWS1/XL8DIRECTIONALITY /AWS1/XL8DIRECTIONALITY¶
The directionality of your terminology resource indicates whether it has one source language (uni-directional) or multiple (multi-directional).
- UNI
The terminology resource has one source language (for example, the first column in a CSV file), and all of its other languages are target languages.
- MULTI
Any language in the terminology resource can be the source language or a target language. A single multi-directional terminology resource can be used for jobs that translate different language pairs. For example, if the terminology contains English and Spanish terms, it can be used for jobs that translate English to Spanish and Spanish to English.
When you create a custom terminology resource without specifying the directionality, it behaves as uni-directional terminology, although this parameter will have a null value.
Queryable Attributes¶
File¶
The file containing the custom terminology data. Your version of the AWS SDK performs a Base64-encoding on this field before sending a request to the AWS service. Users of the SDK should not perform Base64-encoding themselves.
Accessible with the following methods¶
| Method | Description |
|---|---|
GET_FILE() |
Getter for FILE, with configurable default |
ASK_FILE() |
Getter for FILE w/ exceptions if field has no value |
HAS_FILE() |
Determine if FILE has a value |
Format¶
The data format of the custom terminology.
Accessible with the following methods¶
| Method | Description |
|---|---|
GET_FORMAT() |
Getter for FORMAT, with configurable default |
ASK_FORMAT() |
Getter for FORMAT w/ exceptions if field has no value |
HAS_FORMAT() |
Determine if FORMAT has a value |
Directionality¶
The directionality of your terminology resource indicates whether it has one source language (uni-directional) or multiple (multi-directional).
- UNI
The terminology resource has one source language (for example, the first column in a CSV file), and all of its other languages are target languages.
- MULTI
Any language in the terminology resource can be the source language or a target language. A single multi-directional terminology resource can be used for jobs that translate different language pairs. For example, if the terminology contains English and Spanish terms, it can be used for jobs that translate English to Spanish and Spanish to English.
When you create a custom terminology resource without specifying the directionality, it behaves as uni-directional terminology, although this parameter will have a null value.
Accessible with the following methods¶
| Method | Description |
|---|---|
GET_DIRECTIONALITY() |
Getter for DIRECTIONALITY, with configurable default |
ASK_DIRECTIONALITY() |
Getter for DIRECTIONALITY w/ exceptions if field has no valu |
HAS_DIRECTIONALITY() |
Determine if DIRECTIONALITY has a value |