Description: In LibreOffice 7.5, the text alignment issue with strikethrough is happened again. In this case both Tangut and Nuosu scripts get affected again. Steps to Reproduce: 1. Insert text boxes with vertical text layout set 2. Insert Nuosu and Tangut sample texts respectively 3. See the error Actual Results: All these characters shift to right relative to the strikethrough. Expected Results: In vertical text layout, all upright glyphs should be proper aligned as the following sample: https://drafts.csswg.org/css-writing-modes-4/#vertical-metrics Reproducible: Always User Profile Reset: No Additional Info: Version: 7.5.4.2 (X86_64) / LibreOffice Community Build ID: 36ccfdc35048b057fd9854c757a8b67ec53977b6 CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: zh-CN (zh_CN); UI: zh-CN Calc: threaded Test font: Nuosu SIL https://software.sil.org/nuosu/ Tangut N4694 http://www.ccamc.co/fonts_tangut.php
Created attachment 188096 [details] Test file
Created attachment 188097 [details] Screenshot
Created attachment 188098 [details] Test font You can get all test fonts here.
Is this a regression? If so when was it working correctly?
I saw it have been fixed in 7.2.
Bibisected to: commit ba03e033d1be4bc49f2a8d6afbeecd381507b242 Author: Khaled Hosny <khaled@aliftype.com> Date: Fri Sep 30 18:36:59 2022 +0200 vcl: Use font’s underline/strike position and size These are font bugs. Nuosu SIL has OS/2.yStrikeoutPosition = 512 and Tangut N4694 has it = 249 and both values are too low. This also affects horizontal text. I suggest you report this issue to upstream font developers. You can also restore the old behavior by adding the font family names to FontsDontUseUnderlineMetrics from expert configuration.
Dear Volga, 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://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug