Class GlossaryInputConfig (3.2.1) 

GlossaryInputConfig(mapping=None, *, ignore_unknown_fields=False, **kwargs)

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