Created attachment 132208 [details] comparison MSO 2010 and LibreOffice 5.4 Steps to reproduce: 1. Open attachment 52268 [details] from bug 41728 2. Check cells' height in 'Your Personal Details' table Reproduced in Version: 5.4.0.0.alpha0+ Build ID: 4ba483beccc99d336d0e0bec47b5fd6823b16c16 CPU threads: 4; OS: Linux 4.8; UI render: default; VCL: gtk3; Locale: ca-ES (ca_ES.UTF-8); Calc: group
Regression introduced by: author Caolán McNamara <caolanm@redhat.com> 2015-04-07 13:57:39 (GMT) committer Caolán McNamara <caolanm@redhat.com> 2015-04-07 20:09:05 (GMT) commit b7fff04ad728369a09a5e1a5cfbe494cf388317b (patch) tree 9c3314d5c0a991f0a7e19a31a96800c256b70b88 parent 5ba54aacd5318fbf9b9f0589a090f717c53833c7 (diff) Resolves: tdf#90504 0x7 chars in .doc are not always cell/row ends fdo65094-2.doc shows that a 0x7 isn't always a row/cell end only a 0x7 that is right at the end of the paragraph range is a real row/cell end this I believe will remove the last crashtester .doc crash Bisected with bibisect-50max Adding Cc: to Caolán McNamara
** 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 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
Reproduced 6.5+ but also 4.4 and 3.5. Cells looked better on fileopen in LO 3.3 but fields couldn't be filled. Test Windows. MSO also opens that DOC as read-only and fields can be filled only after Edit. Xisco, this was marked by you as a regression from 5.0. Please check bibisect.
(In reply to Timur from comment #3) > Please check bibisect. The problem here is that the content cannot fit in the available space (designed to hold a single number), so it has to expand down. The problem in 5.0 was that some content doubled up in the same cell. But that is different from the problem today, so comment 1's bibisect is not correct. The problem started in 5.2 with bibisect-linux-64-5.2 commit 6caad8eefd49e5ec5721f8ac8cf78cd01a32b44d source commit 975c833943bab627eb461457ab1df35744b291cd Author: Akash Jain on Thu Apr 21 20:42:23 2016 +0530 Upgrade harfbuzz version from 0.9.40 to 1.2.6 I expect that the size of U+2002 (EN space) must have increased (since that is the placeholder used in these cells).
repro 7.6+
caolanm->jluth: do you think both writer and word are using the same placeholders and writer is getting a wider result than word? Or is it more complicated than that?
(In reply to Caolán McNamara from comment #6) > caolanm->jluth: do you think both writer and word are using the same > placeholders and writer is getting a wider result than word? My comment was based on pure speculation - simply based on hearing the word "harfbuzz". I have zero insight into any real details.
If EN space is missing from the font, HarfBuzz will synthesize it (use space glyph but with adjusted width). Older LibreOffice/MS Office didn’t do that and would fallback to a different font. The version of Arial Narrow that comes with macOS does not indeed have EN space. $ hb-shape /System/Library/Fonts/Supplemental/Arial\ Narrow.ttf -u 2002,0031,0032 [space=0+1024|one=1+934|two=2+934] So indeed the synthesized En-space is slightly larger than the width of the digits.
EN space is an odd choice, though, if the purpose is to have space that is equal to digits (figures), since there is already U+2007 FIGURE SPACE for that, and HarfBuzz’s synthesized glyph uses the width of the digits: $ hb-shape /System/Library/Fonts/Supplemental/Arial\ Narrow.ttf -u 2007,0031,0032 [space=0+934|one=1+934|two=2+934]