...
| Configuration Option | Description |
|---|---|
| Styles | Configure specific paragraph styles to not be extracted during the translation. |
| Colors | Select one or more text colors to be excluded as text is extracted for translation. |
| Segments | Mark specific text segments as translatable or not translatable when found by the system. Depending on the segment and chosen translation option, the segment will either be extracted for translation or ignored. Regular expressions may be entered in the system to protect entire segments or just terms with the file. These segments or terms will not be extracted for translation and be taken into account during the wordcount step. In the translation editor, they will appear as tags and can be used to protect parts of texts that should not be translated, but should still appear in the translated document. A good example, is entering terms or regular expressions to protect brand names or confidential content like software codes. |
| Words or Terms | Configure single words, terms, or segments to be excluded from the translation. Any text captured by regular expressions is converted into markup and not modified. A description may be added to avoid confusion. When no description is added, the original text will appear upon hovering over the markup. This feature is useful to protect certain terms that must not be modified by the translator. For instance the company name, or technical references etc... |
Fonts Tab
The Fonts Tab may be used to replace fonts for certain lanaguage specific translation scenarios.
| Configuration Option | Description |
|---|---|
| Replace font when translating into Japenese, Chinese, Korean and similar. | Applies when the target language is Asian language only, as the original document often contains non-compatible fonts that translate into unreadable text. Some fonts cannot correctly display Asian characters. If they are used in a document translated into Japanese the final document will be unreadable. This option forces Word to use a user-defined font for the Asian texts if there is not any compatible font defined. |
| Replace font when translating into Arabic, Hebrew, Farsi and other "complex script" languages. | Applies when the target language is a "complex script" language. This prevents uncompatible fonts in the original document from becoming unreadable text. Some fonts cannot correctly display complex script language characters such as Arabic. If they are used in a document translated into Japanese (for example) the final document will be unreadable. This option forces Word to use a user-defined font for the complex script texts if there is not any compatible font defined. |
| Replace all fonts in the translated document. | An option for translating between languages where different scripts and fonts exist. In some cases the used fonts are not compatible with the target language thus causing the text to be unreadable. This option informs the system to replace all fonts so that the translated document is easy to read. An OCR conversion can create a Word file consisting of extensive font changes. As a result, the document in Wordbee will contain a vast amount of markups. This option may be used to override the fonts of the document by a single user-defined font to drastically reduce the markups. |
Reduce Markup Tab
The Reduce Markup Tab may be used to substantially reduce markup for improved tranlsation memory hits and less work for your translators. Please note that removing markup can result in minor differences between fonts and text styles.
...