# Okapi Framework - Filters ## Trados-Tagged RTF Filter
- Overview - Processing Details - Limitations |
Filters | Developer's Guide | Okapi Framework

If you are using an Okapi Tool after the M9 release, you should be using the wiki online help:
http://www.opentag.com/okapi/wiki/index.php?title=Trados-Tagged_RTF_Filter

## Overview

The Trados-Tagged RTF Filter is an Okapi component that implements the `IFilter` interface for RTF files prepared with the Trados translation layer of styles. The filter is implement in the class `net.sf.okapi.filters.rtf.RTFFilter` of the Okapi library.

This is a filter for READING ONLY and supports only RTF files where inline codes are represented with Trados styles (not RTF with "normal" formatting).

### Trados-Tagged RTF format

A Trados-Tagged RTF document is an RTF file that has special Trados styles associated to different parts of the content and has segmentation markers.

Note that a "normal" RTF file translated with Trados and showing segment is not a full Trados-Tagged RTF because the formatting information are true RTF codes rather than some code inside the text with the `tw4wInternal` style. That is you see the selected text in bold rather than see the `<b>` and `</b>` tags. An example of Trados-Tagged RTF is an HTML document where all the HTML tags are visible and are marked with either the `tw4wInternal` (red) or `tw4wExternal` (gray) style.

## Processing Details

### Input Encoding

The filter decides which encoding to use for the input document using the following logic:

- The document has encoding information defined for each font in the document. The default encoding is also normally declared in the document.
- If there is no default encoding declared, the encoding specified by the user is used as the default.

### Segmentation

Only the text marked by the Trados segmentation markers is taken into account. Any text outside the segments markers are ignored.

he file may or may not contain translation.

## Limitations

This is a READING ONLY filter. This filter does not generate an output corresponding to the input. It must be used for input only.

The filter understands only inline codes that are represented with Trados styles (not RTF with "normal" formatting).