If a cell's number format language has been set, saving the sheet as XLSX and reopening it resets this manual setting to Locale seting in Options - Language Settings - Languages To reproduce: 1. Create a new spreadsheet, add a number to a cell 2. Format->Cells... (Ctrl+1) -> on Numbers tab, set Language to something other than Default 3. Save the file as XLSX and reopen Expected Results: The language set in step 2 should stay Actual Results: The language of the cell's number format is now reset to default Tested with Version: 5.2.1.2 (x64) Build ID: 31dd62db80d4e60af04904455ec9c9219178d620 CPU Threads: 4; OS Version: Windows 6.1; UI Render: default; Locale: ru-RU (ru_RU); Calc: group
Reproducible. Win10x64 Version: 5.2.2.2 (x64) Build ID: 8f96e87c890bf8fa77463cd4b640a2312823f3ad CPU Threads: 4; OS Version: Windows 6.19; UI Render: GL; Locale: es-ES (es_ES); Calc: CL Version: 5.3.0.0.alpha0+ Build ID: ed5ca17dce1d088ce3fbbb3a30f748ba92cd07d9 CPU Threads: 4; OS Version: Windows 6.19; UI Render: GL; TinderBox: Win-x86@42, Branch:master, Time: 2016-10-09_05:40:51 Locale: es-ES (es_ES); Calc: CL
This is likely a OOXML limitation as Excel only allows you to set the number format locale for date, time and special number formats. @Eike: Your thoughts?
I believe Excel does not support different locales in all number formats. Also ECMA-376-1:2016 Office Open XML does not indicate such thing at page 1783 ff. "18.8.31 numFmts (Number Formats)". The locale / language ID modifier is mentioned only with dates and currencies. I don't have Excel at hand for the next weeks, someone could try if it accepts something like [$-409]0.00 for en-US, or [$-407]0,00 for de-DE, or maybe [$-407]0.00 (in an otherwise English environment to accept the decimal separator) and if so whether such survives save/reload.
** 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
No support in the format indeed; NOTABUG.