Created attachment 49267 [details] Subtending marks -- works with gedit Brief: With OpenType rendering, only one digit following a subtending mark (U+0600 .. U+0605, or U+06DD) is rendered correctly; 2nd and following digits are rendered normally. Extended description: Subtending marks (U+0600 .. U+0605, U+06DD) are typically followed by digits which, assuming appropriate font logic (OpenType, Graphite, etc), are then rendered with small glyphs positioned within (or above or below) the subtending mark. These are rendered correctly by gedit -- see attached "Subtending Marks -- gedit.jpg". NB: The font Scheherazade v1.0005 from https://scripts.sil.org/arabicfonts has the OpenType logic for subtending marks U+0600..U+0603 and U+06DD, and was used for this testing. Any implementation will have limits on the number of digits supported -- Scheherazade supports up to 2, 3, or 4 digits depending on the subtending mark. I've also included writer doc "Subtending Marks.ODT" which contains test data. LibreOffice 3.4.1 running on Windows appears to depend on Uniscribe for rendering, and works correctly for the digits from the Arabic block (U+0660 .. U+0669 and U+06F0 .. U+06F9) but not for the "Latin" digits (U+0030 .. U+0039). Nothing you can do about this. However: Writer from LibreOffice 3.4.1 on UBuntu 11.04 fails to correctly render more than one digit. That is, the first digit after the subtending mark is correct, subsequent digits are not. See attached "Subtending Marks -- Writer.jpg" Bob
Created attachment 49268 [details] Subtending marks -- fails with Writer
Created attachment 49269 [details] Subtending marks -- test document
This looks very suspiciously like a bug in ICU layout engine (which is what LO use on Linux). The only other application using ICU that I've is XeTeX, but there not even the first correct. This even seems to affect only Scheherazade, other fonts like Amiri (http://www.amirifont.org, disclaimer: mine) or even Arabic Typesetting seem to work fine (though both have different limit on the number digits than Scheherazade).
[This is an automated message.] This bug was filed before the changes to Bugzilla on 2011-10-16. Thus it started right out as NEW without ever being explicitly confirmed. The bug is changed to state NEEDINFO for this reason. To move this bug from NEEDINFO back to NEW please check if the bug still persists with the 3.5.0 beta1 or beta2 prereleases. Details on how to test the 3.5.0 beta1 can be found at: http://wiki.documentfoundation.org/QA/BugHunting_Session_3.5.0.-1 more detail on this bulk operation: http://nabble.documentfoundation.org/RFC-Operation-Spamzilla-tp3607474p3607474.html
reproduced in LibO 3.6.0 master on Fedora 64 bit
** 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 (4.4.1 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 *If 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-04-18
This still an issue, and if anyone wants to work in this, it is because GenericSalLayout::ApplyDXArray() is messing with glyph positioning. This code is broken beyond by design and the only way to fix it is by killing it and fixing all use sites to not need it.
Still fails on LO 4.4.2.2 Note that Scheherazade is now at version 2.020 (see http://scripts.sil.org/scheherazade for latest) and the OpenType logic has been improved to be more robust with different rendering systems. However the font now includes Graphite tables and, since the default rendering for LO is with Graphite enabled, one might be fooled into thinking the bug has been fixed. But the problem is with OpenType logic. To force LO to disable Graphite and thus render Scheherazade with OpenType, run it with environment variable SAL_DISABLE_GRAPHITE=1.
** 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.1.5 or 5.2.1 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 If 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 helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20160920
Still an issue, should be fixed when bug 89870 is fixed.