Description: Month predictive input, smart completion, show abbreviated month although original words are not abbreviated. Fr Langage. Steps to Reproduce: 1.Enter vertically a list of month - Janvier, février, mars, avril ... décembre (don't forget accentuated letter, so the function doesn't work) 2.Select the cells with mouse and put the mouse cursor on the black little square, click left, and move the cursor to the left next column. The selection area is stretched. 3.You should see the predictive input show some abbreviated input. Actual Results: Août is transformed in sept.Juin in Juil. Expected Results: Août should be transformed in September, not Sept. Reproducible: Always User Profile Reset: No Additional Info: This behaviour doesn't occur when you stretch selection to the down next cells See attachment. Version: 6.0.7.3 Build ID: 1:6.0.7-0ubuntu0.18.04.2 CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: x11; Locale: fr-FR (fr_FR.UTF-8); Calc: group
Created attachment 149536 [details] Screenshot calc autocompletion preddictive input Screenshot calc autocompletion preddictive input
You can stretch the selection to the left or right column of course.
If you have a look in the core/i18npool/source/localedata/data/fr_FR.xml localdata file, you can see that the abbreviated name and the fullname are the same, it occurs for mai and mars, see belowL (you can see similar example in the de_DE.xml file) If you have a mix between full name and abbreviated name, LO thinks it's the full name which is used. I've tried to set the cell type to "Date" and 'Décember' format (month only) : no effect. Extract of local file : <Month> <MonthID>mar</MonthID> <DefaultAbbrvName>mars</DefaultAbbrvName> <DefaultFullName>mars</DefaultFullName> </Month> (...) <Month> <MonthID>may</MonthID> <DefaultAbbrvName>mai</DefaultAbbrvName> <DefaultFullName>mai</DefaultFullName> </Month>
confirmed in Version: 6.1.5.2 Build-ID: 10(Build:2) CPU-Threads: 4; BS: Linux 4.12; UI-Render: Standard; VCL: gtk3_kde5; Gebietsschema: de-DE (de_DE.UTF-8); Calc: group threaded
Dear Regis Perdreau, 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
Dear Regis Perdreau, 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