Using Version: 7.5.0.2 (X86_64) / LibreOffice Community Build ID: c0dd1bc3f1a385d110b88e26ece634da94921f58 CPU threads: 12; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: ru-RU (ru_RU); UI: en-US Calc: CL threaded so the UI is en-US, but the locale is ru-RU I try to enter this: 2/3 and it accepts it as a *text*. This is the problem #1 (why? the entry doesn't conflict with the default date acceptance pattern of "D.M.Y;D.M.;D/M/"). Then I try 0 2/3 and get "2/3", as wanted. But if I try 0 123/4 I get unexpected "123" (while the cell is auto-formatted as "# ?/?"). This is the problem #2, which *maybe* relates to the space being thousands separator? When I pre-format the cell to use en-US in its number formats, it works as expected (123/4, as well as 0 123/4, both give 30 3/4).
Reproduced as described, except for 123/4 in en-US number formatting: it also displays as a string ("123/4", left-aligned). Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: e125e6623fa1c0f39d927bb37547ca6d1e299cb1 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: ru-RU (en_AU.UTF-8); UI: en-US Calc: threaded Same in: Version: 6.1.0.3 Build ID: efb621ed25068d70781dc026f7e9c5187a4decd1 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk2; Locale: en-AU (en_AU.UTF-8); Calc: group threaded
Dear Mike Kaganski, 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