Okapi Components

Overview

The INX Filter is an Okapi component that implements the Okapi Filter Interface for Adobe InDesign Interchange files. INX is XML-based, but it has been designed in such a way that is impossible to apply generic XML text processes to it, it needs a specific filter. You do not need Adobe InDesign to use this filter.

The specification of INX can be found here: http://partners.adobe.com/public/developer/en/indesign/sdk/working_with_inx_file_format.pdf

This filter has no parameters.

Filter Properties

The properties for the XML Filter are the following:

Processing Details

Extracted Text

The filter extracts any text that is in <pcnt> elements and starts with "c_". The text may contain processing instructions, they are set as inline codes.

The flow of the text in <pcnt> elements does not always reflect a correct linguistic flow: sentences may get split. Because of the structure of the INX file that requires to preserve all information to be read back correctly, no effort is made to re-structure the flow of the text.

Input Encoding

The filter uses the XML encoding declaration mechanism to guess automatically the encoding of the input file:

• If a BOM is found, the encoding is UTF-16 or UTF-8.
• Then, if there is en encoding declaration at the top of the file, the encoding specified there is used.
• Otherwise the file is assumed to be in UTF-8.

The encoding defined by the user in the call to the filter is not used at all.

Output Encoding

INX files are in UTF-8. This is enforced and the encoding specified by the user for the output file is ignored.

Rewriting

When writing out the processed XML document, the filter may make some changes to the document:

• Any formatting characters (multiple white-spaces, line-breaks, etc.) in the starting or empty tags are removed and attributes are reformatted.

• Attribute values are always output with double-quotes regardless what delimiter was used in the original document.