Interface GlossaryInputConfigOrBuilder (2.1.13) 

public interface GlossaryInputConfigOrBuilder extends MessageOrBuilder

Implements

MessageOrBuilder

Methods

getGcsSource()

public abstract GcsSource getGcsSource()

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.

.google.cloud.translation.v3beta1.GcsSource gcs_source = 1;

Returns
Type Description
GcsSource

The gcsSource.

getGcsSourceOrBuilder()

public abstract GcsSourceOrBuilder getGcsSourceOrBuilder()

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.

.google.cloud.translation.v3beta1.GcsSource gcs_source = 1;

Returns
Type Description
GcsSourceOrBuilder

getSourceCase()

public abstract GlossaryInputConfig.SourceCase getSourceCase()
Returns
Type Description
GlossaryInputConfig.SourceCase

hasGcsSource()

public abstract boolean hasGcsSource()

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.

.google.cloud.translation.v3beta1.GcsSource gcs_source = 1;

Returns
Type Description
boolean

Whether the gcsSource field is set.