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
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present on a currently supported version of LibreOffice (5.0.4 or later) https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2015-12-20
Dear Shriramana Sharma, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Dear Shriramana Sharma, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
It is been 10 years and these combining marks are included in Unicode 14, so the original issue is no longer reproducible. I think I know what was breaking the encoded combining marks, though, so if you can make a different test with characters that are still unencoded, I might be able to finally fix it.