When choosing to export a job as XML, there are two options for the 'one2edit Translation' format:

1. one2edit Translation
2. one2edit Translation (Absolute Tagging)

The difference between these formats is how the text-styling is represented in the XML tags. Such tagging is required so that the correct styling can be maintained post-translation.

The format that you choose would depend on how your external translation tools work with the formats.

• The "Absolute Tagging" file-format (.o2ea) is the more "traditional" XML format. This format also leads to larger file sizes and is, therefore, the more memory-intensive format.
• The .o2et file-format, on the other hand, generally has a smaller, more efficient file-size.

You can find out which format is right for your external translation tool by simply trying out each format with your TM System.

NOTE:
Both formats are valid XML. The following steps explain the technical differences between each.

This XML format allows for the overlapping of style tags within the XML.

To do this without invalidating the XML, each of the tags is a self-closing tag, using numbers to match where the style begins and ends.

• A style is opened with an <oX/> tag, where "o" stands for "open", and "X" is a digit. The opening tag will also contain parameters about the styling itself.
• The associated closing tag for that style is <cX/>, where "c" stands for "close", and X is the corresponding digit.
• The overall paragraph style is defined outside of the text segment area. The only styles that are covered by these styling tags are local styles and overrides.

An example of some text ("Ready in 5 Min") styled in this manner is:

	<o1 name="cUnderline" value="1"/>Ready <o2 name="cColor" value="Red"/>in<c1/> 5 Min<c2/>

The above tagged text will render in this way:

Ready in 5 Min

The underline starts before the word "Ready", and ends after the word "in". The color change starts before the word "in", and ends after the word "Min".

There are two overlapping styling "sections" above – one for the underline, and one for the red color.

This format optimizes the number of styling tags required throughout an exported XML file, helping to reduce both the file size and the time taken to re-import the translated XML file.

This XML format uses absolute tagging to remove the need for style tags to overlap within the XML.

Styles are opened with a <style> tag, and closed with a </style> tag.

• Tags must open and close regularly within XML in order for the XML to be valid. This means that every time the style changes in the document, a <style> tag pair must be closed and another one opened.
• It also means that every <style> tag pair must contain the full description of the styling for that portion of the segment.

An example of some text ("Ready in 5 Min") styled in this manner is:

	<style name="ParaStyle,cUnderline" value="bullets,1">Ready </style><style name="ParaStyle,cUnderline,cColor" value="bullets,1,Red">in</style><style name="ParaStyle,cColor" value="bullets,Red"> 5 Min</style>

The above tagged text will render in this way:

Ready in 5 Min

As you can see, this is the same text as in the example above, where the words "Ready in" are underlined, and the words "in 5 Min" are colored red.

The difference between this method and the last is that there are now three sections of styling – one for "Ready", one for "in", and one for "5 Min".

You can see that this method will lead to larger XML file sizes, which may increase the time taken to re-import the translated XML file.