Arabic is sometimes written with diacritical vowel marks, which are placed either above or below each letter of the word. Many multipurpose fonts, which are not designed specifically for Arabic, place some of these marks in the empty space between lines, outside of the space reserved for line height. Writing Arabic in LibreOffice Writer, these marks don't become visible while typing but only after the page view has changed once.
See the attached series of screenshots, where the first screenshot has been taken while typing. The first letter of the first word (reading from right to left) should have two diacritical marks: ء and a diagonal line above the letter: أَ. Only the lower half of the ء mark is visible and the diagonal line not at all. The second letter of the same word has a circle on top of it but only the lower half of it is visible. Equally so for the third word of the sentence بِبَرْنَامِجِ, where the last letter of the word has a diagonal line below, but it is not visible at all. The second screenshot has been taken after I scrolled the page down by a couple of screens and then scrolled back. Now all the diacritics are shown as they should. In the third screenshot I have deleted all of the text I typed but as you can see, some parts of the diacritics are still visible above the line. If I scroll down and back, they would disappear. If you want to test it yourself, the sentence I wrote reads "أَكْتُبُ هُنَا بِبَرْنَامِجِ لِيبَرْ أُفِيسْ".
This problem is similar to https://bugs.documentfoundation.org/show_bug.cgi?id=85426 but does not involve fixing line spaces. Even the font I'm using is different (DejaVu Sans).
This bug was first reported on Launchpad for LO 188.8.131.52 on Ubuntu 17.10 at: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1772451 . After my initial report, I have upgraded to LO 184.108.40.206 and can still reproduce the problem. On Launchpad, I was advised to file this report separately from 85426, as I was not sure whether it is exactly the same issue or just related to it.
Steps to Reproduce:
1. Type Arabic text with full vowel marks, including low diacritics under letters extending below the baseline and high diacritics on top of high letters.
2. Remove the text by pressing backspace.
Many vowel diacritics or parts of them become visible only after the view is changed, and removing a character sometimes leaves the diacritic or part of it visible on the screen, although textually it doesn't exist anymore.
All diacritics should become visible as the user is typing and be removed from the screen as soon as the characters are removed.
User Profile Reset: No
Created attachment 144556 [details]
Writer view as the user is typing
Created attachment 144557 [details]
Writer view after the screen has changed
Created attachment 144558 [details]
Writer view after removing the text
Created attachment 145298 [details]
Just an example image from master build
Created attachment 145299 [details]
The example document used for the screenshot
That image is from todays master…
And yes - those two selections is just one done with a single cursor.
Probably this should have been a new bug…
CPU-Threads: 64; BS: Linux 3.16; UI-Render: Standard; VCL: x11;
Gebietsschema: de-DE (de_DE.UTF-8); Calc: threaded
Arch Linux 64-bit
Build ID: d357ea1d1ff95cb5ce2ee6b4828afa2484707256
CPU threads: 8; OS: Linux 4.18; UI render: default; VCL: gtk3_kde5;
Locale: fi-FI (fi_FI.UTF-8); Calc: threaded
Built on 28 September 2018
We are probably clipping the drawn area at line height instead of font’s OS/2 table Win metrics, which is wrong IMO.
That some glyphs or parts of glyph can be outside ascender/descender is not unusual and is font specific. We shouldn’t be clipping based on line height either way.
(In reply to Khaled Hosny from comment #9)
> That some glyphs or parts of glyph can be outside ascender/descender is not
> unusual and is font specific. We shouldn’t be clipping based on line height
> either way.
So essentially the same issue as bug 99578 and bug 105346 ?
(In reply to Buovjaga from comment #10)
> (In reply to Khaled Hosny from comment #9)
> > That some glyphs or parts of glyph can be outside ascender/descender is not
> > unusual and is font specific. We shouldn’t be clipping based on line height
> > either way.
> So essentially the same issue as bug 99578 and bug 105346 ?
Most likely yes, the same underlying issue.
Not completely confident, if we should close as dupe, so using See also for now.
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!
Still reproducible on:
Build ID: libreoffice-220.127.116.11-snap1
CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3;
Locale: fi-FI (fi_FI.UTF-8); UI-Language: en-US