Struct aws_sdk_translate::types::TerminologyData
source · #[non_exhaustive]pub struct TerminologyData {
pub file: Blob,
pub format: TerminologyDataFormat,
pub directionality: Option<Directionality>,
}
Expand description
The data associated with the custom terminology. For information about the custom terminology file, see Creating a 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: 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: 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 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.
Implementations§
source§impl TerminologyData
impl TerminologyData
sourcepub fn file(&self) -> &Blob
pub fn file(&self) -> &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.
sourcepub fn format(&self) -> &TerminologyDataFormat
pub fn format(&self) -> &TerminologyDataFormat
The data format of the custom terminology.
sourcepub fn directionality(&self) -> Option<&Directionality>
pub fn directionality(&self) -> 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 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.
source§impl TerminologyData
impl TerminologyData
sourcepub fn builder() -> TerminologyDataBuilder
pub fn builder() -> TerminologyDataBuilder
Creates a new builder-style object to manufacture TerminologyData
.
Trait Implementations§
source§impl Clone for TerminologyData
impl Clone for TerminologyData
source§fn clone(&self) -> TerminologyData
fn clone(&self) -> TerminologyData
1.0.0 · source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source
. Read moresource§impl Debug for TerminologyData
impl Debug for TerminologyData
source§impl PartialEq for TerminologyData
impl PartialEq for TerminologyData
source§fn eq(&self, other: &TerminologyData) -> bool
fn eq(&self, other: &TerminologyData) -> bool
self
and other
values to be equal, and is used
by ==
.impl StructuralPartialEq for TerminologyData
Auto Trait Implementations§
impl Freeze for TerminologyData
impl RefUnwindSafe for TerminologyData
impl Send for TerminologyData
impl Sync for TerminologyData
impl Unpin for TerminologyData
impl UnwindSafe for TerminologyData
Blanket Implementations§
source§impl<T> BorrowMut<T> for Twhere
T: ?Sized,
impl<T> BorrowMut<T> for Twhere
T: ?Sized,
source§fn borrow_mut(&mut self) -> &mut T
fn borrow_mut(&mut self) -> &mut T
source§impl<T> Instrument for T
impl<T> Instrument for T
source§fn instrument(self, span: Span) -> Instrumented<Self>
fn instrument(self, span: Span) -> Instrumented<Self>
source§fn in_current_span(self) -> Instrumented<Self>
fn in_current_span(self) -> Instrumented<Self>
source§impl<T> IntoEither for T
impl<T> IntoEither for T
source§fn into_either(self, into_left: bool) -> Either<Self, Self>
fn into_either(self, into_left: bool) -> Either<Self, Self>
self
into a Left
variant of Either<Self, Self>
if into_left
is true
.
Converts self
into a Right
variant of Either<Self, Self>
otherwise. Read moresource§fn into_either_with<F>(self, into_left: F) -> Either<Self, Self>
fn into_either_with<F>(self, into_left: F) -> Either<Self, Self>
self
into a Left
variant of Either<Self, Self>
if into_left(&self)
returns true
.
Converts self
into a Right
variant of Either<Self, Self>
otherwise. Read more