Hi there! Are you looking for the official Deno documentation? Try docs.deno.com for all your Deno learning needs.

TerminologyData

import type { TerminologyData } from "https://aws-api.deno.dev/v0.3/services/translate.ts?docs=full";

The data associated with the custom terminology.

interface TerminologyData {
Directionality?: Directionality | null;
File: Uint8Array | string;
Format: TerminologyDataFormat;
}

§Properties

§
Directionality?: Directionality | null
[src]

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.

§
File: Uint8Array | string
[src]

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
[src]

The data format of the custom terminology.