Class: Google::Cloud::Translate::V3::InputConfig

Inherits:
Object
  • Object
show all
Extended by:
Protobuf::MessageExts::ClassMethods
Includes:
Protobuf::MessageExts
Defined in:
proto_docs/google/cloud/translate/v3/translation_service.rb

Overview

Input configuration for BatchTranslateText request.

Instance Attribute Summary collapse

Instance Attribute Details

#gcs_source::Google::Cloud::Translate::V3::GcsSource

Returns Required. Google Cloud Storage location for the source input. This can be a single file (for example, gs://translation-test/input.tsv) or a wildcard (for example, gs://translation-test/*). If a file extension is .tsv, it can contain either one or two columns. The first column (optional) is the id of the text request. If the first column is missing, we use the row number (0-based) from the input file as the ID in the output file. The second column is the actual text to be translated. We recommend each row be <= 10K Unicode codepoints, otherwise an error might be returned. Note that the input tsv must be RFC 4180 compliant.

You could use https://github.com/Clever/csvlint to check potential formatting errors in your tsv file. csvlint –delimiter=’\t’ your_input_file.tsv

The other supported file extensions are .txt or .html, which is treated as a single large chunk of text.

Returns:

  • (::Google::Cloud::Translate::V3::GcsSource)

    Required. Google Cloud Storage location for the source input. This can be a single file (for example, gs://translation-test/input.tsv) or a wildcard (for example, gs://translation-test/*). If a file extension is .tsv, it can contain either one or two columns. The first column (optional) is the id of the text request. If the first column is missing, we use the row number (0-based) from the input file as the ID in the output file. The second column is the actual text to be translated. We recommend each row be <= 10K Unicode codepoints, otherwise an error might be returned. Note that the input tsv must be RFC 4180 compliant.

    You could use https://github.com/Clever/csvlint to check potential formatting errors in your tsv file. csvlint –delimiter=’\t’ your_input_file.tsv

    The other supported file extensions are .txt or .html, which is treated as a single large chunk of text.



414
415
416
417
# File 'proto_docs/google/cloud/translate/v3/translation_service.rb', line 414

class InputConfig
  include ::Google::Protobuf::MessageExts
  extend ::Google::Protobuf::MessageExts::ClassMethods
end

#mime_type::String

Returns 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.

Returns:

  • (::String)

    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.



414
415
416
417
# File 'proto_docs/google/cloud/translate/v3/translation_service.rb', line 414

class InputConfig
  include ::Google::Protobuf::MessageExts
  extend ::Google::Protobuf::MessageExts::ClassMethods
end