software.amazon.awssdk.services.translate.model

Interface TerminologyData.Builder

All Superinterfaces:

Buildable, CopyableBuilder<TerminologyData.Builder,TerminologyData>, SdkBuilder<TerminologyData.Builder,TerminologyData>, SdkPojo

Enclosing class:

TerminologyData

public static interface TerminologyData.Builder
extends SdkPojo, CopyableBuilder<TerminologyData.Builder,TerminologyData>

Method Summary

Modifier and Type	Method and Description
TerminologyData.Builder	directionality(Directionality directionality) The directionality of your terminology resource indicates whether it has one source language (uni-directional) or multiple (multi-directional).
TerminologyData.Builder	directionality(String directionality) The directionality of your terminology resource indicates whether it has one source language (uni-directional) or multiple (multi-directional).
TerminologyData.Builder	file(SdkBytes file) The file containing the custom terminology data.
TerminologyData.Builder	format(String format) The data format of the custom terminology.
TerminologyData.Builder	format(TerminologyDataFormat format) The data format of the custom terminology.

Methods inherited from interface software.amazon.awssdk.core.SdkPojo

equalsBySdkFields, sdkFields

Methods inherited from interface software.amazon.awssdk.utils.builder.CopyableBuilder

copy

Methods inherited from interface software.amazon.awssdk.utils.builder.SdkBuilder

applyMutation, build

Method Detail

file

TerminologyData.Builder file(SdkBytes 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.

Parameters:

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.

Returns:

Returns a reference to this object so that method calls can be chained together.

format

TerminologyData.Builder format(String format)

The data format of the custom terminology.

Parameters:

format - The data format of the custom terminology.

Returns:

Returns a reference to this object so that method calls can be chained together.

See Also:

TerminologyDataFormat, TerminologyDataFormat

format

TerminologyData.Builder format(TerminologyDataFormat format)

The data format of the custom terminology.

Parameters:

format - The data format of the custom terminology.

Returns:

Returns a reference to this object so that method calls can be chained together.

See Also:

TerminologyDataFormat, TerminologyDataFormat

directionality

TerminologyData.Builder directionality(String 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.

Parameters:

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.

Returns:

Returns a reference to this object so that method calls can be chained together.

See Also:

Directionality, Directionality

directionality

TerminologyData.Builder directionality(Directionality 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.

Parameters:

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.

Returns:

Returns a reference to this object so that method calls can be chained together.

See Also:

Directionality, Directionality