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.
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.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-07 UTC."],[[["\u003cp\u003eThis webpage details the \u003ccode\u003eInputConfig\u003c/code\u003e class within the \u003ccode\u003eGoogle.Cloud.Translate.V3\u003c/code\u003e namespace, specifically version 2.2.0 of the library, which is a crucial component for configuring input for the \u003ccode\u003eBatchTranslateText\u003c/code\u003e request.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003eInputConfig\u003c/code\u003e class is designed to manage the configuration for batch text translation, including handling input from Google Cloud Storage and specifying the mime type of the input files.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003eInputConfig\u003c/code\u003e class has an implementation of the interfaces \u003ccode\u003eIMessage\u003c/code\u003e, \u003ccode\u003eIEquatable\u003c/code\u003e, \u003ccode\u003eIDeepCloneable\u003c/code\u003e, \u003ccode\u003eIBufferMessage\u003c/code\u003e, and its properties include \u003ccode\u003eGcsSource\u003c/code\u003e, \u003ccode\u003eMimeType\u003c/code\u003e, and \u003ccode\u003eSourceCase\u003c/code\u003e, each serving specific roles in managing the input configuration.\u003c/p\u003e\n"],["\u003cp\u003eIt supports various file types for batch translation such as \u003ccode\u003e.tsv\u003c/code\u003e, \u003ccode\u003e.txt\u003c/code\u003e, and \u003ccode\u003e.html\u003c/code\u003e, with \u003ccode\u003e.tsv\u003c/code\u003e files potentially having two columns for text ID and the text itself, which adheres to RFC 4180 compliance.\u003c/p\u003e\n"],["\u003cp\u003eThere are many versions of this specific implementation, including versions 3.9.0 down to 2.2.0, but the main context is based on version 2.2.0.\u003c/p\u003e\n"]]],[],null,[]]
