Rich Text format settings
This page contains settings for Rich Text Format file type (.rtf files).
Styles page
| 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.
|
Non-translatable texts page
Available options are:
| Non-translatable texts |
Non-translatable texts are delimited by special start and end characters as follows:
|
Footnotes page
| Non-translatable footnotes | You can include footnotes in the translation or ignore them. By default, the text from footnotes is extracted for translation. Footnotes that have a footnote mark listed in this dialog box are extracted as tags. You can also choose Treat all footnote marks as tags. If you do not choose this, the footnote mark is handled as ordinary text. |
Text boxes page
| Order of text box processing | Specify the order in which text boxes are handled. |
Common page
| 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 | 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 If Asian text font is not displayed, Asian elements in the | ||||||
| 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).
| ||||||
| Treat soft returns as structure tags | You can treat soft returns (break tags) as segment breaks, or extract them for translation as text. | ||||||
| Treat special characters as inline placeholder tags | Examples of special characters are non-breaking space, tab and discretionary hyphen. You can treat these characters as text or as tags. If you treat them as tags they are put into inline tags. Em dash and en dash are always treated as text. | ||||||
| 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 filters that SDL Trados Studio uses to open Word files which have the tw4winMark style defined. Consider enabling this option if you want Studio to use the Word 2000-2003 filter (for 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, Studio will not use Word filters to process the file, but will use the Bilingual Workbench filter instead. If you disable this option (the default setting) and the Bilingual Workbench filter processes a non-bilingual file that has this style defined, the filter will produce an empty | ||||||
| Process hyperlinks |
Options are:
|