Struct aws_sdk_translate::model::TerminologyData [−][src]
#[non_exhaustive]pub struct TerminologyData {
pub file: Option<Blob>,
pub format: Option<TerminologyDataFormat>,
pub directionality: Option<Directionality>,
}
Expand description
The data associated with the custom terminology.
Fields (Non-exhaustive)
This struct is marked as non-exhaustive
Struct { .. }
syntax; cannot be matched against without a wildcard ..
; and struct update syntax will not work.file: Option<Blob>
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.
format: Option<TerminologyDataFormat>
The data format of the custom terminology.
directionality: Option<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 terms in English and Spanish, then it can be used for jobs that translate English to Spanish and jobs that translate 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.
Implementations
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.
The data format of the custom terminology.
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 terms in English and Spanish, then it can be used for jobs that translate English to Spanish and jobs that translate 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.
Creates a new builder-style object to manufacture TerminologyData
Trait Implementations
This method tests for self
and other
values to be equal, and is used
by ==
. Read more
This method tests for !=
.
Auto Trait Implementations
impl RefUnwindSafe for TerminologyData
impl Send for TerminologyData
impl Sync for TerminologyData
impl Unpin for TerminologyData
impl UnwindSafe for TerminologyData
Blanket Implementations
Mutably borrows from an owned value. Read more
Attaches the provided Subscriber
to this type, returning a
WithDispatch
wrapper. Read more
Attaches the current default Subscriber
to this type, returning a
WithDispatch
wrapper. Read more