Module types

Data structures used by operation inputs/outputs.

Modules

builders

Builders

error

Error types that Amazon Translate can respond with.

Structs

AppliedTerminology

The custom terminology applied to the input text by Amazon Translate for the translated text response. This is optional in the response and will only be present if you specified terminology input in the request. Currently, only one terminology can be applied per TranslateText request.

Document

The content and content type of a document.

EncryptionKey

The encryption key used to encrypt this object.

InputDataConfig

The input configuration properties for requesting a batch translation job.

JobDetails

The number of documents successfully and unsuccessfully processed during a translation job.

Language

A supported language.

OutputDataConfig

The output configuration properties for a batch translation job.

ParallelDataConfig

Specifies the format and S3 location of the parallel data input file.

ParallelDataDataLocation

The location of the most recent parallel data input file that was successfully imported into Amazon Translate.

ParallelDataProperties

The properties of a parallel data resource.

Tag

A key-value pair that adds as a metadata to a resource used by Amazon Translate.

Term

The term being translated by the custom terminology.

TerminologyData

The data associated with the custom terminology. For information about the custom terminology file, see Creating a Custom Terminology.

TerminologyDataLocation

The location of the custom terminology data.

TerminologyProperties

The properties of the custom terminology.

TextTranslationJobFilter

Provides information for filtering a list of translation jobs. For more information, see ListTextTranslationJobs.

TextTranslationJobProperties

Provides information about a translation job.

TranslatedDocument

The translated content.

TranslationSettings

Settings to configure your translation output. You can configure the following options:

• Brevity: reduces the length of the translation output for most translations. Available for TranslateText only.

• Formality: sets the formality level of the translation output.

• Profanity: masks profane words and phrases in the translation output.

Enums

Brevity

When writing a match expression against Brevity, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.

Directionality

When writing a match expression against Directionality, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.

DisplayLanguageCode

When writing a match expression against DisplayLanguageCode, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.

EncryptionKeyType

When writing a match expression against EncryptionKeyType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.

Formality

When writing a match expression against Formality, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.

JobStatus

When writing a match expression against JobStatus, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.

MergeStrategy

When writing a match expression against MergeStrategy, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.

ParallelDataFormat

When writing a match expression against ParallelDataFormat, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.

ParallelDataStatus

When writing a match expression against ParallelDataStatus, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.

Profanity

When writing a match expression against Profanity, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.

TerminologyDataFormat

When writing a match expression against TerminologyDataFormat, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.