Description: Text distribution with 'anchor to character' questionable Steps to Reproduce: 1. Open the attached file 2. Look at the text distribution Actual Results: Empty area on page 2 and pag 3. Dragging the anchor a bit and everything shrinks to 3 pages Expected Results: Not sure, starts with the problem where the 'anchor the character' is actually anchored.. Different at edit filesave/reload Reproducible: Always User Profile Reset: No Additional Info: Version: 7.0.0.0.alpha0+ (x64) Build ID: 4475bcd83aac7e033fc5250f268eb922bd471e7b CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: default; VCL: win; Locale: nl-NL (nl_NL); UI-Language: en-US Calc: CL
Created attachment 159722 [details] Example file
I opened attached document with Version: 7.0.0.0.alpha0+ (x64)Build ID: 8c8b3a4f83f67882b284ddc3b3fe10d3fe6dedf4CPU threads: 4; OS: Windows 10.0 Build 18363; UI render: Skia/Raster; VCL: win; Locale: de-DE (de_DE); UI-Language: en-GBCalc: CL Result: 3 pages and no empty spaces. Is it the correct document? => NEEDINFO
Created attachment 159903 [details] Screenshot
Also in LibreOffice 3.3.0 OOO330m19 (Build:6) tag libreoffice-3.3.0.4
Created attachment 159904 [details] Result in LO 7.0.0.0.alpha0+ Document shows three images (screenshot only shows two images)
Created attachment 159906 [details] PDF result (In reply to Dieter from comment #5) > Created attachment 159904 [details] > Result in LO 7.0.0.0.alpha0+ > > Document shows three images (screenshot only shows two images) There is a 'fourth' page
The difference between Telesto's and Dieter's result is due to Dieter missing Netherlands hyphenation package. Telesto: is it possible to create an example file which does not depend on NL hyphenation to display the problem? Or is the problem intimately connected with hyphenation?
(In reply to Buovjaga from comment #7) > The difference between Telesto's and Dieter's result is due to Dieter > missing Netherlands hyphenation package. > > Telesto: is it possible to create an example file which does not depend on > NL hyphenation to display the problem? Or is the problem intimately > connected with hyphenation? Is there a preference? Setting the language to German, and it has the same flaw.. Which slightly unsurprising. Dutch is a germanic language :-). (Might need a Save/file reload after the change) But true, doesn't fail with English and of course Hungarian; the actual document language
(In reply to Telesto from comment #8) > (In reply to Buovjaga from comment #7) > > The difference between Telesto's and Dieter's result is due to Dieter > > missing Netherlands hyphenation package. > > > > Telesto: is it possible to create an example file which does not depend on > > NL hyphenation to display the problem? Or is the problem intimately > > connected with hyphenation? > > Is there a preference? Setting the language to German, and it has the same > flaw.. Which slightly unsurprising. Dutch is a germanic language :-). (Might > need a Save/file reload after the change) > > But true, doesn't fail with English and of course Hungarian; the actual > document language I'm just wondering, if we can come up with a "portable" way to reproduce this, but maybe it is not needed because you reproduced with 3.3.0. I installed hyphen-nl package on Arch Linux and see the same result as you. Arch Linux 64-bit Version: 7.1.0.0.alpha0+ Build ID: bcf8868e031f916473f13bcd1a0835c74cb05de5 CPU threads: 8; OS: Linux 5.8; UI render: default; VCL: kf5 Locale: fi-FI (fi_FI.UTF-8); UI: en-US Calc: threaded Built on 20 August 2020
Dear Telesto, 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