Page Settings 130 x 200mm are imprecisely saved as 130 x 200,01mm. How to reproduce: - Open new document (A4 -> 210 x 297mm) - Format > Page: Change page format to 130 x 200mm + Click OK - Check Format > Page: Page Height is imprecisely saved as 200,01mm Same issue with Insert > Form > Standard > Rectangle - Draw Rectangle - Select Rectangle + Right click "Position and size" - Manually type size width 50mm and size height 50mm and Click OK - Select Rectangle + Right click "Position and size" - Size width is imprecisely saved as 50,01mm and size height as 50,01mm Version: 6.2.5.2 (x64) Build-ID: 1ec314fa52f458adc18c4f025c545a4e8b22c159 CPU-Threads: 4; BS: Windows 6.1; UI-Render: Standard; VCL: win; Gebietsschema: de-DE (de_DE); UI-Sprache: de-DE Calc: threaded
Not reproducible for me with Version: 6.2.5.2 (x64) Build-ID: 1ec314fa52f458adc18c4f025c545a4e8b22c159 CPU-Threads: 4; BS: Windows 10.0; UI-Render: GL; VCL: win; Gebietsschema: de-DE (de_DE); UI-Sprache: de-DE Calc: threaded
Thank you for reporting the bug. it seems you're using an old version of LibreOffice. Could you please try to reproduce it with the latest version of LibreOffice from https://www.libreoffice.org/download/libreoffice-fresh/ ? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the latest version.
Confirm with 6.2.7 (you need to set measurement units to millimeter to see that .01 millimeter difference).
Also reproduced in Version 4.1.0.0.alpha0+ (Build ID: ff140bb6b8b109f14c270ff059f0b8d71dab5d6)
I reproduce in LO 3.5 in bibisect-43all, so I assume inherited from OOo. FYI using 199.999 also rounds up to 200.01. So I see the reported issue, but I don't know why it matters... (Knowing why it matters would be very helpful.)
Dear canned, 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
Still reproduced. Version: 25.2.3.2 (X86_64) / LibreOffice Community Build ID: bbb074479178df812d175f709636b368952c2ce3 CPU threads: 8; OS: Windows 11 X86_64 (10.0 build 26100); UI render: Skia/Raster; VCL: win Locale: ja-JP (ja_JP); UI: ja-JP Calc: CL threaded Jumbo Version: 25.8.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: 6190fe56f72008e0b6d0e502bf94099e72b9d202 CPU threads: 8; OS: Windows 11 X86_64 (build 26100); UI render: default; VCL: win Locale: ja-JP (ja_JP); UI: ja-JP Calc: threaded Could it be an issue with floating-point number processing, rounding, or unit conversion? I've seen similar things occurred in other places where length is entered.