com.google.cloud.translate.v3

Interface GlossaryInputConfigOrBuilder

All Superinterfaces:

MessageLiteOrBuilder, MessageOrBuilder

All Known Implementing Classes:

GlossaryInputConfig, GlossaryInputConfig.Builder

public interface GlossaryInputConfigOrBuilder
extends MessageOrBuilder

Method Summary

Modifier and Type	Method and Description
GcsSource	getGcsSource() Required.
GcsSourceOrBuilder	getGcsSourceOrBuilder() Required.
GlossaryInputConfig.SourceCase	getSourceCase()
boolean	hasGcsSource() Required.

Methods inherited from interface com.google.protobuf.MessageOrBuilder

findInitializationErrors, getAllFields, getDefaultInstanceForType, getDescriptorForType, getField, getInitializationErrorString, getOneofFieldDescriptor, getRepeatedField, getRepeatedFieldCount, getUnknownFields, hasField, hasOneof

Methods inherited from interface com.google.protobuf.MessageLiteOrBuilder

isInitialized

Method Detail

hasGcsSource

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. See documentation for more information -
   [glossaries](https://cloud.google.com/translate/docs/advanced/glossary).
 

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

Returns:

Whether the gcsSource field is set.

getGcsSource

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. See documentation for more information -
   [glossaries](https://cloud.google.com/translate/docs/advanced/glossary).
 

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

Returns:

The gcsSource.

getGcsSourceOrBuilder

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. See documentation for more information -
   [glossaries](https://cloud.google.com/translate/docs/advanced/glossary).
 

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

getSourceCase

GlossaryInputConfig.SourceCase getSourceCase()