Non-exhaustive enums could have additional variants added in future. Therefore, when matching against variants of non-exhaustive enums, an extra wildcard arm must be added to account for any future variants.
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.