The following should be possible:

• There may be special characters inside a file, that need a special font to display correctly (like Wingdings). Theses special characters For xml:
  • Inside segments of an xml file there may be inline tags with a special name and an attribute, that contains the name of a font
  • The name of the tag and the name of the attribute should be configurable in the xml file filter settings of translate5 to use a special font.
• For docx, pptx and idml :
  • If a number of characters inside a text (that will constitute a segment) have a different font assigned, than the font of the rest of the segments: Then the information what font this is will be extracted from the original source files and will be made available for translate5 as attribute of the inline tag, that shows the start and ending of this special inline formatting.
• If this font has been made available to translate5 in the font-management
  • inside these inline tags inside the segment editor the font mentioned in the attribute of the tag will be used to display the characters instead of the usual font of translate5 for segment content
  • Also in the WYWIYG pre-view of the visual the font will be used to display the characters, that are shown inside the inline tags in question inside the segment.
• The fonts need to be provided in the font management of translate5, that needs to be extended for this, since the use case differs a lot regarding its technical requirements from the current font management of the visual feature of translate5.

To implement this we need to:

• Rework the structure of internal tags in translate5's editor, to enable them to influence the style of the characters between them (so far from an HTML point of view each inline tag in translate5 is a stand-alone tag)
• To achieve this, we need to extract the tag name and the attribute content for translate5 into the xliff and coordinate this with what Okapi does on file format conversion.