google_api_translate v0.9.0 GoogleApi.Translate.V3.Model.GlossaryInputConfig View Source
Input configuration for glossaries.
Attributes
gcsSource
(type:GoogleApi.Translate.V3.Model.GcsSource.t
, default:nil
) - 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.
Link to this section Summary
Functions
Unwrap a decoded JSON object into its complex fields.
Link to this section Types
t()
View Sourcet() :: %GoogleApi.Translate.V3.Model.GlossaryInputConfig{ gcsSource: GoogleApi.Translate.V3.Model.GcsSource.t() }
Link to this section Functions
Unwrap a decoded JSON object into its complex fields.