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 / Translation

Why are my translated characters not correct after importing an o2et file?

Created on 25th September 2014 at 11:33 by Jamie O'Connell

There are two potential reasons why the characters/glyphs from your translated XML file (i.e. the file that was translated in your Translation Management System) would display incorrectly:

  1. No Alphabet Font Support
  2. Incorrect Encoding

No Alphabet Font Support

A font often contains only one character set or alphabet. For example, a font may contain only Latin characters/glyphs, meaning that it is only suitable for rendering Latin languages (e.g. English, Spanish, German, etc.). Such a font would not be able to render text that was typed in Greek, Cyrillic, Japanese, etc. (i.e. different alphabets).

For this reason, it is important to create styles for each target alphabet into which your document will be translated or localised. This will allow a one2edit™ user to easily choose the correct style for the target language if missing characters are displayed. Furthermore, languages are different lengths to one another, so the styles can also be used to automatically adjust fitting options (such as tracking, text size, etc.) for a language, while staying within the brand guidelines. In such a case, users would not need to be given direct access to fitting values.

Incorrect Encoding

When translating an XML file (e.g. the .o2et file-format from one2edit™) inside a Translation Management System (TMS), the encoding of the characters in the exported XML file must be correct. The .o2et files are encoded in UTF-8, as described at the top of the XML file when it is opened in a text editor.

For example, if I were to encode the Greek character Epsilon in UTF-8 encoding, it would show up as "ε" or "Ε" (upper or lower case). However, were I to encode this character in ISO 8859-1 encoding (i.e. languages from Western Europe and the Americas), it would instead show up as "ε" or "Ε"

If you do see such symbolic representations of the characters in your translation, please ensure that the encoding of the exported XML files from your TMS is set to UTF-8.

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