Rich Text Format (Deprecated) Settings

Styles page

Available options are:

Styles

Specify which text is to be excluded from translation, based on the text's style. Text that is excluded is represented by a tag in the final document. You can choose whether this tag should be a structure tag or an inline tag.

Note: Style names are case sensitive.

Non-translatable texts page

Available options are:

Non-translatable texts

Non-translatable texts are delimited by special start and end characters as follows:

Start text

The characters that start the text to be excluded. The first character must be an opening brace {.

Example: {MACROBUTTON

End text

Enter the characters that end of the text to be excluded. The final character must be a closing brace} .

Text boxes page

Available options are:

Order of text boxes

Specify the order in which text boxes are handled.

Common page

Available options are:

Extract comments text for translation

You can extract comments for translation or skip them.

Extract document properties for translation

Document properties include the document's author, its creation date, and so on. You can extract these properties for translation or ignore them.

Display complex scripts and Asian text font settings

This has an effect only on Microsoft Windows computers that have Asian language support installed.

If Asian text font is displayed, formatting information is provided by inserting a <cf> ('control formatting') tag in the output text. A large number of such tags can be distracting for translators.

If Asian text font is not displayed, Asian elements in the <cf> tags are switched off and superfluous <cf> tags are hidden.

Process documents containing unaccepted or rejected changes

Usually you do not want to process documents that have tracked changes, because both original and new text is extracted for translation, which is probably not desirable. The problem does not arise if the document does not have tracked changes (even if tracked changes are enabled). The action by default is to process a file containing tracking changes.

Note: The file type software cannot open a Word document that has Track changes enabled.

Treat soft returns as structure tags (treat break tags as document structure)

You can treat soft returns (break tags) as segment breaks, or extract them for translation as text.

Bookmarks (Process bookmarks as tag pairs)

If set, a bookmark is extracted as a tag pair, otherwise it is extracted as two standalone tags.

Process files with tw4winMark style

Use this option to change the file types that StudioStudio uses to open Word files which have the tw4winMark style defined. Consider enabling this option if you want StudioStudio to use the Microsoft Word 2000-2003 file type (for .doc files) or the Microsoft Word 2007-2013 file type (for .docx files) for these files instead of using the Bilingual Workbench file type.

This is relevant if you might have Word files which contain the tw4winMark style but which are not bilingual files.

The presence of tw4winMark style in Word files usually indicates that the file is a bilingual file, produced from Trados Translator's Workbench. So, by default, when a Word document has this style, StudioStudio will not use Word file types to process the file, but will use the Bilingual Workbench file type instead.

If you disable this option (the default setting) and the Bilingual Workbench file type processes a non-bilingual file that has this style defined, the file type will produce an empty sdlxliff file with no segments.