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 document provides reference documentation for the \u003ccode\u003eInputConfig\u003c/code\u003e class within the Google Cloud Translation v3 API, detailing its usage in batch text translation requests.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003eInputConfig\u003c/code\u003e class is used to define the input configuration for the \u003ccode\u003eBatchTranslateText\u003c/code\u003e request, offering options such as the Google Cloud Storage location for the input source and the MIME type of the input files.\u003c/p\u003e\n"],["\u003cp\u003eSupported file extensions for input include \u003ccode\u003e.tsv\u003c/code\u003e, \u003ccode\u003e.txt\u003c/code\u003e, and \u003ccode\u003e.html\u003c/code\u003e, each with specific formatting and usage guidelines, and the document offers a tool for checking formatting errors for the \u003ccode\u003e.tsv\u003c/code\u003e file type.\u003c/p\u003e\n"],["\u003cp\u003eThe latest version available is \u003ccode\u003e3.9.0\u003c/code\u003e, with versions going back to \u003ccode\u003e2.2.0\u003c/code\u003e, showing a variety of versions available within the Google Cloud Translation v3 API, and the document provides links to each version.\u003c/p\u003e\n"],["\u003cp\u003e\u003ccode\u003eInputConfig\u003c/code\u003e implements multiple interfaces, including \u003ccode\u003eIMessage\u003c/code\u003e, \u003ccode\u003eIEquatable\u003c/code\u003e, \u003ccode\u003eIDeepCloneable\u003c/code\u003e, and \u003ccode\u003eIBufferMessage\u003c/code\u003e, and is derived from the \u003ccode\u003eobject\u003c/code\u003e class, with some inherited members listed.\u003c/p\u003e\n"]]],[],null,[]]
