https://bugs.documentfoundation.org/show_bug.cgi?id=137440
--- Comment #4 from Bartosz <gan...@poczta.onet.pl> ---
The root cause of wrongly displayed text is lack of implementation of
ETO_GLYPH_INDEX option from EMR_EXTTEXTOUTW record.
ETO_GLYPH_INDEX bit indicates that the codes for characters in an output text
string are
actually indexes of the character glyphs in a TrueType font. Glyph indexes are
font-specific, so to
display the correct characters on playback, the font that is used MUST be
identical to the font used
to generate the indexes.
Generally it is not possible to get right character from Unicode, and it should
be taken directly from TrueType font index. More information:
https://social.msdn.microsoft.com/Forums/windowsdesktop/en-US/5c88ddaf-5dbe-4f81-9c0d-83785798d500/how-to-get-right-unicode-character-when-exttextoutw-called-with-etoglyphindex-set-in-fuoptions?forum=windowssdk
I found also some useful implementation on Qt side, which could be helpful:
https://bugreports.qt.io/browse/QTBUG-40683
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
