Struct aws_sdk_translate::types::builders::TerminologyDataBuilder

#[non_exhaustive]
pub struct TerminologyDataBuilder { /* private fields */ }

A builder for TerminologyData.

Implementations

impl TerminologyDataBuilder

pub fn file(self, input: Blob) -> Self

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.

This field is required.

pub fn set_file(self, input: Option<Blob>) -> Self

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.

pub fn get_file(&self) -> &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.

pub fn format(self, input: TerminologyDataFormat) -> Self

The data format of the custom terminology.

This field is required.

pub fn set_format(self, input: Option<TerminologyDataFormat>) -> Self

The data format of the custom terminology.

pub fn get_format(&self) -> &Option<TerminologyDataFormat>

The data format of the custom terminology.

pub fn directionality(self, input: Directionality) -> Self

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.

pub fn set_directionality(self, input: Option<Directionality>) -> Self

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.

pub fn get_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.

pub fn build(self) -> Result<TerminologyData, BuildError>

Consumes the builder and constructs a TerminologyData. This method will fail if any of the following fields are not set:

• file
• format

Trait Implementations

impl Clone for TerminologyDataBuilder

fn clone(&self) -> TerminologyDataBuilder

Returns a copy of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for TerminologyDataBuilder

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl Default for TerminologyDataBuilder

fn default() -> TerminologyDataBuilder

Returns the “default value” for a type.

impl PartialEq for TerminologyDataBuilder

fn eq(&self, other: &TerminologyDataBuilder) -> bool

This method tests for self and other values to be equal, and is used by ==.

fn ne(&self, other: &Rhs) -> bool

This method tests for !=. The default implementation is almost always sufficient, and should not be overridden without very good reason.

impl StructuralPartialEq for TerminologyDataBuilder