login | sign up

Your session has timed out due to inactivity.

You can go back to the overview without login or use the login form to login again before redirect

Knowledge Base / FAQs - one2edit™ v4 / Translation - v4

What does Absolute Tagging mean when exporting a one2edit™ Translation File?

Created on 08th October 2026 at 10:48 by Jamie O'Connell



There are two options when exporting a translation job from one2edit™ in the one2edit Translation format.

  1. one2edit Translation: a more efficient XML format, based on the XLIFF tagging format.
  2. one2edit Translation (Absolute Tagging): a strict-XML version of the above.

Export Job > Format

There are two options for the one2edit Translation format, as shown.

  • one2edit Translation: an efficient XML format, based on the XLIFF format.
  • one2edit Translation (Absolute Tagging): a strict-XML version of the above. The strict tagging leads to larger file sizes and is, therefore, the more memory-intensive format.

The differences between these two formats is in the XML-tag structure used to maintain the text-styling during the translation process.

The format that you choose depends on what your external translation tools require.

NOTE: Both formats are valid XML. The differences are described below.

one2edit Translation (.o2et)

This format has standalone, self-closing XML tags to manage styling. It uses tag numbers to indicate where a specific style begins and ends.

  • Local styling begins with an <oX/> tag, where "o" stands for "opening", and "X" is a digit. The opening tag also contains the styling as parameters.
  • The associated closing tag for that style is <cX/>, where "c" stands for "closing", and X is the same digit as in the opening tag for this styling.

An example of some text ("Making strong brands even stronger.") styled using this method is:

Making <o1 name="cUnderline" value="1"/>strong brands <o2 name="cColor" value="Red"/>even<c1/> stronger<c2/>.

The above tagged text will render in this way:

Making strong brands even stronger.

  • The underline styling starts before the word "strong", and ends after the word "even".
  • The color change starts before the word "even", and ends after the word "stronger".

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 file.

NOTE: The paragraph style is defined outside of the text segment area. These styling tags are only necessary for local character styles and overrides.

one2edit Translation (Absolute Tagging) (.o2ea)

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

  • Styling opens with a <style> tag. Each opening tag contains the styling information as parameters.
  • Styling is closed with a </style> tag.

Every time the style changes in the document, a pair of styling tags must be closed and another one opened. This means that every pair of styling tags must contain the full description of the styling for that portion of the segment.

An example of some text ("Making strong brands even stronger.") styled in this manner is:

Making <style name="ParaStyle,cUnderline" value="bullets,1">strong brands </style><style name="ParaStyle,cUnderline,cColor" value="bullets,1,Red">even</style><style name="ParaStyle,cColor" value="bullets,Red"> stronger</style>.

The above tagged text will render in this way:

Making strong brands even stronger.

As you can see, this is the same text as in the example above, where:

  • The underline styling starts before the word "strong", and ends after the word "even".
  • The color change starts before the word "even", and ends after the word "stronger".

The difference between this method and the last is that there are now multiple sections of styling – one for "strong brands", one for "even", and one for "stronger".




© 2009-2026 1io BRANDGUARDIAN GmbH · All rights Reserved · Legal / Privacy Policy


top