Package types (3.3.2)

State metadata for the batch translation operation. .. attribute:: state

The state of the operation.

:type: google.cloud.translate_v3.types.BatchTranslateMetadata.State

Stored in the google.longrunning.Operation.response][google.longrunning.Operation.response] field returned by BatchTranslateText if at least one sentence is translated successfully.

The batch translation request. .. attribute:: parent

Required. Location to make a call. Must refer to a caller's project.

Format: projects/{project-number-or-id}/locations/{location-id}.

The global location is not supported for batch translation.

Only AutoML Translation models or glossaries within the same region (have the same location-id) can be used, otherwise an INVALID_ARGUMENT (400) error is returned.

:type: str

Stored in the google.longrunning.Operation.metadata][google.longrunning.Operation.metadata] field returned by CreateGlossary.

Request message for CreateGlossary. .. attribute:: parent

Required. The project name.

:type: str

Stored in the google.longrunning.Operation.metadata][google.longrunning.Operation.metadata] field returned by DeleteGlossary.

Request message for DeleteGlossary. .. attribute:: name

Required. The name of the glossary to delete.

:type: str

Stored in the google.longrunning.Operation.response][google.longrunning.Operation.response] field returned by DeleteGlossary.

The request message for language detection. .. attribute:: parent

Required. Project or location to make a call. Must refer to a caller's project.

Format: projects/{project-number-or-id}/locations/{location-id} or projects/{project-number-or-id}.

For global calls, use projects/{project-number-or-id}/locations/global or projects/{project-number-or-id}.

Only models within the same region (has same location-id) can be used. Otherwise an INVALID_ARGUMENT (400) error is returned.

:type: str

The response message for language detection. .. attribute:: languages

A list of detected languages sorted by detection confidence in descending order. The most probable language first.

:type: Sequence[google.cloud.translate_v3.types.DetectedLanguage]

The response message for language detection. .. attribute:: language_code

The BCP-47 language code of source content in the request, detected automatically.

:type: str

The Google Cloud Storage location for the output content. .. attribute:: output_uri_prefix

Required. There must be no files under 'output_uri_prefix'. 'output_uri_prefix' must end with "/" and start with "gs://", otherwise an INVALID_ARGUMENT (400) error is returned.

:type: str

The Google Cloud Storage location for the input content. .. attribute:: input_uri

Required. Source data URI. For example, gs://my_bucket/my_object.

:type: str

Request message for GetGlossary. .. attribute:: name

Required. The name of the glossary to retrieve.

:type: str

The request message for discovering supported languages. .. attribute:: parent

Required. Project or location to make a call. Must refer to a caller's project.

Format: projects/{project-number-or-id} or projects/{project-number-or-id}/locations/{location-id}.

For global calls, use projects/{project-number-or-id}/locations/global or projects/{project-number-or-id}.

Non-global location is required for AutoML models.

Only models within the same region (have same location-id) can be used, otherwise an INVALID_ARGUMENT (400) error is returned.

:type: str

Represents a glossary built from user provided data. .. attribute:: name

Required. The resource name of the glossary. Glossary names have the form projects/{project-number-or-id}/locations/{location-id}/glossaries/{glossary-id}.

:type: str

Input configuration for glossaries. .. attribute:: gcs_source

Required. Google Cloud Storage location of glossary data. File format is determined based on the filename extension. API returns [google.rpc.Code.INVALID_ARGUMENT] for unsupported URI-s and file formats. Wildcards are not allowed. This must be a single file in one of the following formats:

For unidirectional glossaries:

• TSV/CSV (.tsv/.csv): 2 column file, tab- or comma-separated. The first column is source text. The second column is target text. The file must not contain headers. That is, the first row is data, not column names.

• TMX (.tmx): TMX file with parallel data defining source/target term pairs.

  For equivalent term sets glossaries:

• CSV (.csv): Multi-column CSV file defining equivalent glossary terms in multiple languages. The format is defined for Google Translation Toolkit and documented in Use a glossary <https://support.google.com/translatortoolkit/answer/6306379?hl=en>__.

  :type: google.cloud.translate_v3.types.GcsSource

Input configuration for BatchTranslateText request. .. attribute:: mime_type

Optional. Can be "text/plain" or "text/html". For .tsv, "text/html" is used if mime_type is missing. For .html, this field must be "text/html" or empty. For .txt, this field must be "text/plain" or empty.

:type: str

Request message for ListGlossaries. .. attribute:: parent

Required. The name of the project from which to list all of the glossaries.

:type: str

Response message for ListGlossaries. .. attribute:: glossaries

The list of glossaries for a project.

:type: Sequence[google.cloud.translate_v3.types.Glossary]

Output configuration for BatchTranslateText request. .. attribute:: gcs_destination

Google Cloud Storage destination for output content. For every single input file (for example, gs://a/b/c.[extension]), we generate at most 2 * n output files. (n is the # of target_language_codes in the BatchTranslateTextRequest).

Output files (tsv) generated are compliant with RFC 4180 except that record delimiters are '\n' instead of '\r\n'. We don't provide any way to change record delimiters.

While the input files are being processed, we write/update an index file 'index.csv' under 'output_uri_prefix' (for example, gs://translation-test/index.csv) The index file is generated/updated as new files are being translated. The format is:

input_file,target_language_code,translations_file,errors_file, glossary_translations_file,glossary_errors_file

input_file is one file we matched using gcs_source.input_uri. target_language_code is provided in the request. translations_file contains the translations. (details provided below) errors_file contains the errors during processing of the file. (details below). Both translations_file and errors_file could be empty strings if we have no content to output. glossary_translations_file and glossary_errors_file are always empty strings if the input_file is tsv. They could also be empty if we have no content to output.

Once a row is present in index.csv, the input/output matching never changes. Callers should also expect all the content in input_file are processed and ready to be consumed (that is, no partial output file is written).

The format of translations_file (for target language code 'trg') is: gs://translation_test/a_b_c\_'trg'_translations.[extension]

If the input file extension is tsv, the output has the following columns: Column 1: ID of the request provided in the input, if it's not provided in the input, then the input row number is used (0-based). Column 2: source sentence. Column 3: translation without applying a glossary. Empty string if there is an error. Column 4 (only present if a glossary is provided in the request): translation after applying the glossary. Empty string if there is an error applying the glossary. Could be same string as column 3 if there is no glossary applied.

If input file extension is a txt or html, the translation is directly written to the output file. If glossary is requested, a separate glossary_translations_file has format of gs://translation_test/a_b_c\_'trg'_glossary_translations.[extension]

The format of errors file (for target language code 'trg') is: gs://translation_test/a_b_c\_'trg'_errors.[extension]

If the input file extension is tsv, errors_file contains the following: Column 1: ID of the request provided in the input, if it's not provided in the input, then the input row number is used (0-based). Column 2: source sentence. Column 3: Error detail for the translation. Could be empty. Column 4 (only present if a glossary is provided in the request): Error when applying the glossary.

If the input file extension is txt or html, glossary_error_file will be generated that contains error details. glossary_error_file has format of gs://translation_test/a_b_c\_'trg'_glossary_errors.[extension]

:type: google.cloud.translate_v3.types.GcsDestination

A single supported language response corresponds to information related to one supported language.

The response message for discovering supported languages. .. attribute:: languages

A list of supported language responses. This list contains an entry for each language the Translation API supports.

:type: Sequence[google.cloud.translate_v3.types.SupportedLanguage]

Configures which glossary should be used for a specific target language, and defines options for applying that glossary.

The request message for synchronous translation. .. attribute:: contents

Required. The content of the input in string format. We recommend the total content be less than 30k codepoints. Use BatchTranslateText for larger text.

:type: Sequence[str]

A single translation response. .. attribute:: translated_text

Text translated into the target language.

:type: str