Created attachment 64775 [details] Test material to reproduce and test the bug While working on a proposal to encode two characters to Brahmi (https://sites.google.com/site/jamadagni/files/utcsubmissions/12226-brahmi-two-tamil-characters-proposal.pdf), I found that some versions of LibO on some platforms had a bug by which an unencoded codepoint would not combine properly. I had proposed to disunify the Tamil Brahmi virama from 11046 and encode it at 11070, and likewise to disunify the Tamil Brahmi LLA from 11034 and encode it at 11071. However, if I map the glyphs in my fonts to 11070 and 11071, problems are created. See the attachment. It contains a Graphite Brahmi font (under the OFL) in glyph-only and Graphite-enabled forms. The GDL is also included. Test ODTs and the renderings (as PDF) on LibO 3.5.4 on Win XP, LibO 3.5.3 on Linux (Kubuntu Precise) and LibO 3.7.0alpha (LibO~master~2012-06-14_22.09.53_3.7.0alpha0) on Win XP are provided. Only LibO 3.5.4 on Win XP does not have any problems with the un-encoded mappings. LibO 3.5.3 on Linux and LibO 3.7alpha on Win XP do not correctly join LLA to the vowel signs. (LLA line highlighted in blue.) Perhaps some versions of LibO make some assumptions about the encoded or non-encoded status of characters? Which is why 11071 Tamil Brahmi LLA does not combine properly? But this does not explain why I had no problems with the equally un-encoded 11070 Tamil Brahmi Virama? Or how the version numbers (see above) work out (I mean, bug seen in 3.5.3 and 3.7 but not in 3.5.4)? Graphite by definition does not make any assumptions about the encoding or non-encoding of any characters. If LibO is to provide true Graphite integration, it should also not make any assumptions about input characters when they are being rendered using Graphite. Please fix this so that we can use LibO for rare Indic scripts via Graphite (which we can't expect OpenType support for). Thank you for your great work on LibO and Graphite!
I really suspect that this isn't our bug and is something to do with how Linux is dealing with the font. Does the font work correctly in other software outside of LibO inside of Linux? Marking as NEEDINFO just for that information, once you provide it, please mark as NEW as it's clear that there is in fact a difference and if you can confirm that it's not Linux wide problem we can mark as NEW. Very similar to a bug that I reported quite some time ago about Telugu font, I closed it myself thinking it was a problem with Linux not with LibO: https://bugs.freedesktop.org/show_bug.cgi?id=48303 Thanks for your patience and help with getting this bug triaged
Dear Bug Submitter, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INVALID due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/FDO/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team
Created attachment 87544 [details] UTF-8 encoded text file containing relevant sample and output of current HB trunk Sorry for the delay in replying. I have attached a UTF-8 encoded input file I fed to hb-view of HarfBuzz (NG, latest trunk) built with Graphite2 support on Kubuntu Precise 64 bit. I have also attached the output PNG. You will see that there are no problems in rendering. OTOH latest LibO 4.1.1.2 release under same Kubuntu still shows the problem.
See previous comment. Sorry for the extra post but there was no way to reset the status and do the attachment at once.
Appropriate status is UNCONFIRMED as we need confirmation from an independent QA person :) Thanks for the attachment
Created attachment 93256 [details] Results of testing on LibO 4.2 release I tested the material against the recent release of LibO 4.2. I confirm that the bug still exists. Please can some QA person also confirm this so this can be fixed soon? It persists since almost two years. Thank you!
Created attachment 108450 [details] PDF export using 4.4.0.0 alpha1 from Oct 26 I confirm that the problem persists. The problematic highlighted row "lla" is not the same as in the HarfBuzz .png. Win 7 64-bit dev build Version: 4.4.0.0.alpha1+ Build ID: fa58d91094895a530648630fa64b8724ea1e4305 TinderBox: Win-x86@39, Branch:master, Time: 2014-10-26_09:30:18
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.