Created attachment 138053 [details] Writer – Manually set scale factor. Build ID: 5.4.3.2-1.fc27 CPU threads: 2; OS: Linux 4.13; UI render: default; VCL: gtk3; Locale: en-GB (en_GB.UTF-8); Calc: group Scale factor 1, is not set right (At least on Writer and Calc, only Canonical applications I uses) which means that therefore real sizes are not set correctly for value 1; reasons can be either operating system handled scale factor 1 is not set right, or in case too Libreoffice handles independently its own scale factor, that scale factor 1 is not set right. Therefore on a 14.1'-inched laptop screen, whose default resolution is 1280 x 800 pix (16:10), while scale is set at value 1, on screen displayed sizes do not match real world sizes. Indeed in order to match real world sizes. value has to be set manually, (8right-click Zoom-level on bottom tool-bar) to 1.18, which as illustrated in attachment corresponds to 118 %. Expected should be either that system or application that handles scale factor 1 to be set right as it is a requirement to get rights proportions of a document's content. In case Linux operating system and Libreoffice too handle scale factors, and are active at the same time, therefore they mustn't interfere one with another.
So to test you take a physical ruler and measure the dimensions from the screen?
Correction 13.3-inched WideScreen (13.2" x 7.1"). Physical ruler was not available so package used as application ruler on Fedora 27 is screenruler-0.96-8.fc27.noarch. In order to get a an acceptable accuracy, on Screenruler's I had to make some changes: Settings -> Check Custom settings and set same amount of pixels per inches for both Horizontal and vertical (rights settings for my screen, 1280/13.2" x 800/7.1" which makes at closest 113 x 113, which allows an accuracy of -/+ 1 mm). Ruler application's size unit set to cm. Target paper format set to A4 (in cm. 21.00 x 29.70) in Writer. Actual results: Ruler indicates 17.9 cm as measure of document horizontal side (corresponds to 118 % on Writer scale) while 21.0 cm is expected.
Correction: 13.3-inched WideScreen (11.3" x 7.1"), just for information; it has no consequence on results from measured dimensions.
After confirming I had the opposite problem (have to reduce zoom to match reality), I did some digging. It may be fundamentally impossible to fix this without doing a huge renovation. https://ask.libreoffice.org/en/question/9400/how-can-i-get-actual-page-size-on-monitor-screen/ https://forum.openoffice.org/en/forum/viewtopic.php?p=254905&sid=382389010d1eb80f7dcd02bcb7fefa33#p254905 "the paper size is measured in twips" https://en.wikipedia.org/wiki/Twip
Version: 6.0.2.1.0+ – Build ID: 6.0.2.1-2.fc28 – CPU threads: 2; OS: Linux 4.16; UI render: default; VCL: gtk3; – Locale: en-GB (en_GB.UTF-8); Calc: group Issue still alive. Upgraded from Fedora v. 27 to v. 28 beta.
** 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
If the os/DE "Scale factor 1" equates to a zoom of 100% there is no expectation in LibreOffice that zoom to 100% is rendering to screen in "actual" measurements. Zoom is to 100% of the applications internal scaling which works in screen independent TWIPS(1/1,440"), or worse PIXELS -- how big is a pixel? You can adjust the application's zoom so that it will actually measure out on the screen at 100%. Or you could adjust your os/DE screen resolution reducing/increasing the effective pixel size--until the applications 100% zoom matches real world measurement. But that will impact other use of the desktop. Some potential for improvement as LO has been forced for HiDPI support to identify the DPI that a combination of screen size and pixel resolution supports so the UI can be appropriately scaled. But the actual scale of a 100% zoom would still not be directly tested/validated--just rendered "close enough". Printing & Export, unlike screen rendering, are directly written out with size/scale values relevant to the device/file format. IMHO, this is not a valid bug and is just a manifestation of the graphics framework and application interface.
Dear ricky.tigg, 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://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
Refer to Comment 7 if internally considered valid.
Dear ricky.tigg, 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