Created attachment 132429 [details] Example of Cut-off text After https://cgit.freedesktop.org/libreoffice/core/commit/?id=38b0c24fa5cbb4246e03d77ac022dfdc9fdede03 Related: tdf#105454 DOCX import: fix unwanted enabled-by-default kerning Tight .docx textboxes now have text cut-off. .doc files are affected by a different commit. I'm seeing this behavior with both the Cambria and Calibri fonts under Windows. By manually going Edit Style -> Position -> Checking "Pair kerning", I can restore the cut-off text.
Created attachment 132430 [details] Example of Cut-off text before and after default kern setting changed
Created attachment 132431 [details] .doc also cut-off
Adding Cc: to Miklos Vajna
Thanks for the report, but I don't think this is a regression, sorry. Open the file in Word, press Ctlr-D to open the Font dialog -> go to the Advanced tab -> Kerning for fonts checkbox is not checked. If you see a file where kerning in LO is (after the above commit) disabled, but not in MSO, that's a regression. Enabling kerning is a workaround for your problem as far as I see. I also agree it's a bug that the text is cut off, though. Given that the DOC and DOCX import code is separate, it may make sense to open two bugreports for the two bug documents.
Miklos,
Miklos or Khaled, Yes, that makes sense that the kerning issue was hiding this spacing issue. Any idea on how to tease out the cause of this? To see if the fonts are taking up too much space, if the table is too narrow, or if the overlap detection needs to be relaxed a bit?
One thing you can do yourself is exporting to PDF using LO and MSO and then compare those PDFs. If the table is too narrow, you'll see that clearly with this technique.
attachment 107160 [details] from bug 84536 has also changed after 38b0c24fa5cbb4246e03d77ac022dfdc9fdede03
Same problem with attachment 101256 [details] from bug 80155
** 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
Still repo on Version: 6.2.0.0.alpha0+ Build ID: 55b128760e8e7fb732b4627f3120ea5cba8755ce CPU threads: 4; OS: Windows 10.0; UI render: default;
Dear Luke, 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
Created attachment 152893 [details] Simple Example to Show Issue with Effect Spacing Steps to reproduce: 1. In Word, create a 1 cell table 2. Type a few words 3. Fit table to contents 4. Change Font Effect to small caps 5. Open in Writer Reproducible with Version: 6.4.0.0.alpha0+ (x64) Build ID: 2f2f4767089512c34514896bc37823f9310e9dd4
Per Comment 7, I exported my original bugdoc to to PDF using LO and MSO. The resulting dimensions of the table were identical. The issue is with font spacing not the table being too narrow.
*** Bug 137985 has been marked as a duplicate of this bug. ***
Bug 137985 is fileopen of DOCX attachment 81684 [details] from bug 81522. Same for DOC variant from bug 66119 or bug 115649. With many examples, I raise to High.
Created attachment 167017 [details] attachment 81684 [details] compared attachment 81684 [details] doesn't have kerning in MSO, seen good with kerning in LO. But that's a workaround, not a solution. Table is too tight for content, same if Resize is turned off, same if font Cambria changed to Liberation in MSO, same with small or regular caps (so bug title not good). Seems that LO doesn't read or apply "Automatically resize to fit contents". Table can be manually widened in MSO to be good in LO (not a solution). (IMO it's better to keep DOC and DOCX here. Easy to open another if one is resolved.)
Funny (or sad for QA, depends how you look) about this bug is that examples attachment 132429 [details], attachment 107160 [details], attachment 81684 [details] are all Demo-Hayden-Management which has multiple bug reports which are not See Also connected not original attachment name was used. attachment 101256 [details] from bug 80155 also has "Automatically resize to fit contents".