[upstream] Diacritical marks become visible only after changing view in Writer

Bug #1772451 reported by Miikka-Markus Alhonen
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
LibreOffice
Confirmed
Medium
libreoffice (Ubuntu)
Triaged
Medium
Unassigned

Bug Description

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 "أَكْتُبُ هُنَا بِبَرْنَامِجِ لِيبَرْ أُفِيسْ".

As a user, I would expect the diacritics to be visible as soon as I type them, and for them to be removed from the screen immediately when I delete the word.

Description: Ubuntu 17.10
Release: 17.10

libreoffice-writer:
  Installed: 1:5.4.6-0ubuntu0.17.10.1
  Candidate: 1:5.4.6-0ubuntu0.17.10.1
  Version table:
 *** 1:5.4.6-0ubuntu0.17.10.1 500
        500 http://mr.archive.ubuntu.com/ubuntu artful-updates/main amd64 Packages
        100 /var/lib/dpkg/status
     1:5.4.5-0ubuntu0.17.10.5 500
        500 http://security.ubuntu.com/ubuntu artful-security/main amd64 Packages
     1:5.4.1-0ubuntu1 500
        500 http://mr.archive.ubuntu.com/ubuntu artful/main amd64 Packages

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: libreoffice-writer 1:5.4.6-0ubuntu0.17.10.1
ProcVersionSignature: Ubuntu 4.13.0-41.46-generic 4.13.16
Uname: Linux 4.13.0-41-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.8
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon May 21 16:17:03 2018
InstallationDate: Installed on 2017-02-13 (462 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=fi_FI.utf-8
 SHELL=/bin/bash
SourcePackage: libreoffice
UpgradeStatus: Upgraded to artful on 2017-11-05 (196 days ago)

Revision history for this message
Miikka-Markus Alhonen (malhonen) wrote :
Revision history for this message
Miikka-Markus Alhonen (malhonen) wrote :

Second screenshot showing all the diacritics in full.

Revision history for this message
Miikka-Markus Alhonen (malhonen) wrote :

Third screenshot showing remnants of diacritics after the text has already been removed.

Revision history for this message
Olivier Tilloy (osomon) wrote :

Sorry for the lack of feedback until now, Miikka.

I am not sure how to reproduce the issue on my end to confirm it, since this involves typing the example sentence character by character, which I can't do as I can't read/write Arabic.

The screenshots you attached demonstrate pretty clearly the problem, however.

Are you able to test libreoffice 6.0.3 on Ubuntu 18.04 and confirm that the bug is still present?

A quick search through upstream bugs related to diacritics didn't raise any similar issue, would you mind filing a bug report at https://bugs.documentfoundation.org/enter_bug.cgi?product=LibreOffice&format=guided and linking to it here so we can track its resolution? Thanks!

Revision history for this message
Miikka-Markus Alhonen (malhonen) wrote :

The same problem does occur on LO 6.0.3 on Ubuntu 18.04. After looking through Arabic-specific issues reported upstream, I did find this: https://bugs.documentfoundation.org/show_bug.cgi?id=85426 . I think it's the same issue, although the bug title only mentions "fixing line space" and a specific font. I'm using a different font and I didn't fix any line spaces, just started typing in a new document. Do you think I should file this problem separately?

Revision history for this message
Olivier Tilloy (osomon) wrote :

If unsure it is the same issue, I think it's worth filing a new one, and mentioning the existing one in the description. People doing the triaging upstream will decide whether to merge both issues.

Revision history for this message
In , Miikka-Markus Alhonen (malhonen) wrote :

Description:
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 5.4.6.2 on Ubuntu 17.10 at: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1772451 . After my initial report, I have upgraded to LO 6.0.3.2 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.

Actual Results:
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.

Expected Results:
All diacritics should become visible as the user is typing and be removed from the screen as soon as the characters are removed.

Reproducible: Always

User Profile Reset: No

Additional Info:

Revision history for this message
In , Miikka-Markus Alhonen (malhonen) wrote :

Created attachment 144556
Writer view as the user is typing

Revision history for this message
In , Miikka-Markus Alhonen (malhonen) wrote :

Created attachment 144557
Writer view after the screen has changed

Revision history for this message
In , Miikka-Markus Alhonen (malhonen) wrote :

Created attachment 144558
Writer view after removing the text

Revision history for this message
Miikka-Markus Alhonen (malhonen) wrote :
Changed in df-libreoffice:
importance: Unknown → Medium
status: Unknown → New
Changed in libreoffice (Ubuntu):
status: New → Triaged
importance: Undecided → Medium
Revision history for this message
In , Jan-Marek Glogowski (jmglogow) wrote :

Created attachment 145298
Just an example image from master build

Revision history for this message
In , Jan-Marek Glogowski (jmglogow) wrote :

Created attachment 145299
The example document used for the screenshot

Revision history for this message
In , Jan-Marek Glogowski (jmglogow) wrote :

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…

Version: 6.2.0.0.alpha0+
Build-ID: b0eab4b2d2761139ecf5191252dfa8005cd29508
CPU-Threads: 64; BS: Linux 3.16; UI-Render: Standard; VCL: x11;
Gebietsschema: de-DE (de_DE.UTF-8); Calc: threaded

Revision history for this message
In , Beluga (beluga) wrote :

Repro.

Arch Linux 64-bit
Version: 6.2.0.0.alpha0+
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

Revision history for this message
In , Khaled Hosny (khaledhosny) wrote :

We are probably clipping the drawn area at line height instead of font’s OS/2 table Win metrics, which is wrong IMO.

Revision history for this message
In , Khaled Hosny (khaledhosny) wrote :

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.

Revision history for this message
In , Beluga (beluga) wrote :

(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 ?

Revision history for this message
In , Khaled Hosny (khaledhosny) wrote :

(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.

Revision history for this message
In , Beluga (beluga) wrote :

Not completely confident, if we should close as dupe, so using See also for now.

Changed in df-libreoffice:
status: New → Confirmed
Revision history for this message
In , Qa-admin-q (qa-admin-q) wrote :

Dear vaaydayaasra,

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

Revision history for this message
In , Miikka-Markus Alhonen (malhonen) wrote :

Still reproducible on:

Version: 6.3.2.2
Build ID: libreoffice-6.3.2.2-snap1
CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3;
Locale: fi-FI (fi_FI.UTF-8); UI-Language: en-US
Calc: threaded

summary: - Diacritical marks become visible only after changing view in Writer
+ [upstream] Diacritical marks become visible only after changing view in
+ Writer
Revision history for this message
In , Qa-admin-q (qa-admin-q) wrote :

Dear vaaydayaasra,

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

Revision history for this message
In , Miikka-Markus Alhonen (malhonen) wrote :

Reproducible on:

Version: 7.3.0.3 (x64) / LibreOffice Community
Build ID: 0f246aa12d0eee4a0f7adcefbf7c878fc2238db3
CPU threads: 4; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win
Locale: fr-FR (fr_FR); UI: fr-FR
Calc: CL

Revision history for this message
In , Miikka-Markus Alhonen (malhonen) wrote :

Still repro on:

Version: 7.6.6.3 (X86_64) / LibreOffice Community
Build ID: 60(Build:3)
CPU threads: 4; OS: Linux 6.5; UI render: default; VCL: gtk3
Locale: fi-FI (fi_FI.UTF-8); UI: fi-FI
Ubuntu package version: 4:7.6.6-0ubuntu0.23.10.1
Calc: threaded

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.