https://bugs.documentfoundation.org/show_bug.cgi?id=66916
--- Comment #9 from General Kutuzov <shanshandehongx...@outlook.com> --- (In reply to JC Ahangama from comment #7) > (In reply to Khaled Hosny from comment #6) > > (In reply to General Kutuzov from comment #5) > > > I think integrating XeTeX/XeLaTeX typesetting engine to handle these > > > features can found the way to solve the bug. > > > > We already use the same layout engine used by XeTeX (HarfBuzz) on Linux. > > Your statement that ligatures of simple scripts work fine in OSX and Linux > is true. I have a feeling though that Windows treats only the set of English > ligatures as ligatures of the Simple Script, perhaps continuing the stop-gap > measure used until font makers understood OpenType PUA (Private User Area) > and look-up tables. The English ligatures were assigned the first few > codepoints of PUA. > > Very soon, Unicode refused to assign any more codepoints for specific > ligatures of languages, telling them to follow OT standard. Open Type (now > Open Font) standard allows font foundries to place ligatures in the PUA and > evoke them using look-up tables. There are three kinds of ligatures but > Standard (regular) Ligatures are rendered by a program by default. > > Windows Notepad, All browsers, Abiword, Mac, Linux, LO Write in Linux, > Excel, Gnumeric show standard ligatures correctly. > > Uniquely, MS Word and LO Write do it randomly and intersperse spaces > everywhere and forget to make some ligatures as well. IE was like this until > the latest version, but now fixed. Well, BabelPad (from http://babelstone.co.uk/) also show standard ligatures correctly, I have tested this app with Linux Libertine G, Linux Libertine O, Free Serif, DejaVu Serif. -- You are receiving this mail because: You are the assignee for the bug.
_______________________________________________ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
