Description: Writer inserts awkward black lines when stretching whitespace for justified right-to-left-text in Classical Syriac. Happens in 5.4 and 6.02. Steps to Reproduce: 1. If you are not familiar with Classical Syriac, install Google’s noto-fonts (e.g. sudo apt-get install fonts-noto). Of course, any other Syriac font will do. 2. Enable Complex Text Layout (Tools > Options > Language Settings > Complex Text Layout; Language: "None", there is no option for Ancient Syriac) 3. Create paragraph style (e.g. "Syriac_Justified") with options: "Justify + Text direction right-to-left (horizontal) + Last Line justified. Select "Noto Sans Syriac Estrangela" as CTL-font. 4. Add some Syriac Text and mark it as "Syriac_Justified". Actual Results: Stretched whitespace with black lines. Expected Results: Stretched whitespace should be white. Reproducible: Always User Profile Reset: Yes Additional Info: Version: 6.0.2.1 Build ID: 1:6.0.2~rc1-0ubuntu0.17.10.1~lo1 CPU threads: 4; OS: Linux 4.13; UI render: default; VCL: gtk3; Locale: de-DE (de_DE.UTF-8); Calc: group User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:58.0) Gecko/20100101 Firefox/58.0
Created attachment 140558 [details] Example, otf-file
Created attachment 140559 [details] Example, exported to pdf
Created attachment 140560 [details] example, awkward whitespace marked red
(In reply to Ludwig Meier from comment #3) > Created attachment 140560 [details] > example, awkward whitespace marked red For the first paragraph, I confirm the problem, *but* the third and fourth lines for me do not have the extra black lines. Arch Linux 64-bit Version: 6.0.2.1.0+ Build ID: 6.0.2-1 CPU threads: 8; OS: Linux 4.15; UI render: default; VCL: kde4; Locale: fi-FI (fi_FI.UTF-8); Calc: group
Dear Buovjaga, thanks a lot for replying. In the second line there seem to be no black lines indeed, but the third and fourth line do show the error as well. For example, compare "b-mdbr)" (first word, l. 3) with the same word in the third paragraph (l. 3): The Aleph has an additional black line at the baseline. This is the reason why I added some additional line breaks in the second paragraph, to show that any word seems to be affected by this problem.
That is a result from trying to do Kashida justification for Syriac (like Arabic), but without actually calculating proper Kashida insertion places and inserting it in the expanded word spaces. Simplest fix is not not do Kashida justification for Syriac, but a more through fix is to figure Syriac Kashida insertion logic and properly apply it. I’m going with the former for now.
Khaled Hosny committed a patch related to this issue. It has been pushed to "master": http://cgit.freedesktop.org/libreoffice/core/commit/?id=ae0a3825f5ad06ff8d6ae3cb388e215d8abe2eb7 tdf#116344: Don’t Kashida justify Syriac text It will be available in 6.1.0. The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
(In reply to Khaled Hosny from comment #6) > That is a result from trying to do Kashida justification for Syriac (like > Arabic), but without actually calculating proper Kashida insertion places > and inserting it in the expanded word spaces. Simplest fix is not not do > Kashida justification for Syriac, but a more through fix is to figure Syriac > Kashida insertion logic and properly apply it. I’m going with the former for > now. Dear Khaled, built from source and tested, works fine. Thanks a lot!
*** Bug 117907 has been marked as a duplicate of this bug. ***