Fonts typically do not contain every glyph for every language. 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., as they use different character sets.

For this reason, it is important to pseudo-translate your document into all target languages during design, and to create styles that will support all character sets. This enables one2edit™ users to easily choose suitable styles for their target language if missing characters are displayed.

Furthermore, the styles can also contain fitting options (such as tracking, text size, etc.) for a language, while staying within the brand guidelines. In such a case, users may not need direct access to fitting values.

When translating an XML file (e.g. the .o2et file-format from one2edit™) using a third-party CAT tool, 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, the Greek character Epsilon in UTF-8 encoding is "ε" or "Ε" (upper or lower case). However, the same character in ISO 8859-1 encoding is instead "ε" or "Ε"

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