Created attachment 184642 [details] test ODT with Page Number fields vs other Statistics fields If a Page Number field's numbering format (likely provided by libnumbertext) is not available for a specific language, a replacement string is used. It can be confusing to the user. Steps: 1. Open attachment Results: If the localised formatting is not available for the language set on the field, some fallbacks are used. For example: * "Ordinal-number 1" for format "1st, 2nd, 3rd..." * "Ordinal 1" for format "First, Second, Third..." * "1" for format "One, Two, Three" This is different to what happens with number fields of the Statistics type. For those, the fallback is first the format for LibreOffice's current locale, and then those same fallback strings if the current LO locale doesn't have the format available either. So there are two things to fix: 1) Inconsistency between "Page number" and "Statistics" fields. Fallback sequence should be consistent for all numeric fields. 2) The fallback strings can be improved, especially for non-English speakers. I see two options to replace the strings: A) Fall back to the default numbering "1, 2, 3.." (solution proposed by Khaled in bug 152985 comment 18) B) Or display a (translatable) string that explains the issue to the user, e.g. "[numbering format not available for this language]". More informative as to what the issue is, but not very elegant since this big string is displayed in place of what is often a small number field. A more involved solution that will make it less likely to see a fallback is to modify the Insert Field and Edit Field dialogs so the field's language can be changed in the dialog and only available formats are displayed, like in Calc Format Cell's dialog. However, unless the language can only be changed in the Edit Field dialog, a sensible fallback will still be needed when the language is later changed (for example when changing a whole paragraph's language). More info: The inconsistency in fallback started with 6.2 (previous versions didn't have the intermediate LO locale fallback for Statistics fields): Version: 6.2.0.0.beta1 Build ID: d1b41307be3f8c19fe6f1938cf056e7ff1eb1d18 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3; Locale: en-AU (en_AU.UTF-8); UI-Language: en-US Calc: threaded Still present in master build from today: Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 197e5f81213d14fdcbff40edf73385ecd4cd9815 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded
I confirm it with Version: 7.5.0.2 (X86_64) / LibreOffice Community Build ID: c0dd1bc3f1a385d110b88e26ece634da94921f58 CPU threads: 4; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: en-GB Calc: CL threaded
Dear Stéphane Guillou (stragu), 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 present in Version: 25.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 894563ee0e4032019623a97c313af3d833863b1f CPU threads: 12; OS: Windows 11 X86_64 (build 22631); UI render: Skia/Vulkan; VCL: win Locale: de-DE (de_DE); UI: en-GB Calc: CL threaded