@@ -634,7 +634,7 @@ class OutputConfig(proto.Message):
634634
635635 The format of translations_file (for target language code
636636 'trg') is:
637- ``gs://translation_test/a_b_c\_ 'trg'_translations.[extension]``
637+ ``gs://translation_test/a_b_c_ 'trg'_translations.[extension]``
638638
639639 If the input file extension is tsv, the output has the
640640 following columns: Column 1: ID of the request provided in
@@ -651,10 +651,10 @@ class OutputConfig(proto.Message):
651651 directly written to the output file. If glossary is
652652 requested, a separate glossary_translations_file has format
653653 of
654- ``gs://translation_test/a_b_c\_ 'trg'_glossary_translations.[extension]``
654+ ``gs://translation_test/a_b_c_ 'trg'_glossary_translations.[extension]``
655655
656656 The format of errors file (for target language code 'trg')
657- is: ``gs://translation_test/a_b_c\_ 'trg'_errors.[extension]``
657+ is: ``gs://translation_test/a_b_c_ 'trg'_errors.[extension]``
658658
659659 If the input file extension is tsv, errors_file contains the
660660 following: Column 1: ID of the request provided in the
@@ -667,7 +667,7 @@ class OutputConfig(proto.Message):
667667 If the input file extension is txt or html,
668668 glossary_error_file will be generated that contains error
669669 details. glossary_error_file has format of
670- ``gs://translation_test/a_b_c\_ 'trg'_glossary_errors.[extension]``
670+ ``gs://translation_test/a_b_c_ 'trg'_glossary_errors.[extension]``
671671
672672 This field is a member of `oneof`_ ``destination``.
673673 """
@@ -760,7 +760,7 @@ class DocumentOutputConfig(proto.Message):
760760 example: an input file with URI: ``gs://a/b/c.[extension]``
761761 stored in a gcs_destination bucket with name "my_bucket"
762762 will have an output URI:
763- ``gs://my_bucket/a_b_c\_ [trg]_translations.[ext]``, where
763+ ``gs://my_bucket/a_b_c_ [trg]_translations.[ext]``, where
764764
765765 - [trg] corresponds to the translated file's language code,
766766 - [ext] corresponds to the translated file's extension
@@ -780,7 +780,7 @@ class DocumentOutputConfig(proto.Message):
780780 but have ``glossary_translations`` instead of
781781 ``translations``. For the previous example, its glossary URI
782782 would be:
783- ``gs://my_bucket/a_b_c\_ [trg]_glossary_translations.[ext]``.
783+ ``gs://my_bucket/a_b_c_ [trg]_glossary_translations.[ext]``.
784784
785785 Thus the max number of output files will be 2 (Translated
786786 document, Glossary translated document).
@@ -1888,17 +1888,17 @@ class BatchDocumentOutputConfig(proto.Message):
18881888
18891889 The naming format of translation output files follows (for
18901890 target language code [trg]): ``translation_output``:
1891- ``gs://translation_output/a_b_c\_ [trg]_translation.[extension]``
1891+ ``gs://translation_output/a_b_c_ [trg]_translation.[extension]``
18921892 ``glossary_translation_output``:
1893- ``gs://translation_test/a_b_c\_ [trg]_glossary_translation.[extension]``.
1893+ ``gs://translation_test/a_b_c_ [trg]_glossary_translation.[extension]``.
18941894 The output document will maintain the same file format as
18951895 the input document.
18961896
18971897 The naming format of error output files follows (for target
18981898 language code [trg]): ``error_output``:
1899- ``gs://translation_test/a_b_c\_ [trg]_errors.txt``
1899+ ``gs://translation_test/a_b_c_ [trg]_errors.txt``
19001900 ``glossary_error_output``:
1901- ``gs://translation_test/a_b_c\_ [trg]_glossary_translation.txt``
1901+ ``gs://translation_test/a_b_c_ [trg]_glossary_translation.txt``
19021902 The error output is a txt file containing error details.
19031903
19041904 This field is a member of `oneof`_ ``destination``.
0 commit comments