Description: On systems with LibO set to use the comma (,) as a decimal separator, the formula bar in writer insists that numbers are entered using the dot (.) as a decimal separator Steps to Reproduce: 1. Open writer, assure that the locale is set so as to use the comma as a decimal separator 2. Create a table 3. Write a number with decimal digits into a cell using the comma as the decimal separator (e.g. 67,20) 4. Use the Table->Number format function to assure that the number is correctly interpreted as such, with the correct magnitude 5. Now, go to another cell. Enter "=" or "F2" so that the formula bar opens 6. Enter the same number as above with the same formatting (e.g., 67,20) 7. Now, go to another cell. Enter "=" or "F2" so that the formula bar opens 8. Enter the same number as above, now using the dot as the decimal separator (e.g., 67.20) 3. Actual Results: Libreoffice writer at point 6 interpretes the number as if there were no decimal separator (e.g., 6720). At point 8 it interprets the number correctly Expected Results: At 6 Writer should have interpreted the number considering the decimal separator. At 8 it should not have. Incidentally, note that the formula bar in calc works as expected, differently from the one in writer. Reproducible: Always User Profile Reset: No Additional Info: [Information automatically included from LibreOffice] Locale: en-US Module: TextDocument [Information guessed from browser] OS: Linux (All) OS is 64bit: yes Note that the automatically included information above is incorrect. If I go to the LibO Tools->Options->Language Settings->Languages, then I have en-US as the user interface setting, but Italian as the Locale. Builds ID: LibreOffice 5.4.2.1 User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:55.0) Gecko/20100101 Firefox/55.0
Can't reproduce it with German as language Step 6: writer interprets the number correct Step 8: writer changes from 67.20 to 6720 I changed the language in the "Format Number" dialog to Italian and everything still was correct. Version: 5.4.2.1 (x64) Build-ID: dfa67a98bede79c671438308dc9036d50465d2cb CPU-Threads: 4; Betriebssystem:Windows 6.19; UI-Render: GL; Gebietsschema: de-DE (de_DE); Calc: group
Please, try with US user interface and German locale.
I tried it with the following settings: Language settings: User Interface: English (USA) Locale setting: German Decimal seperator key: Same as local setting Settings in Format Number dialog Category: Number Format: Standard Language: German I followed the steps described in the bug report and recieved the same result as Sergio in the bug report => Set to NEW What I recognized is that the decimal separator key was wrong (dot instead of comma). So I think the bug might be related with a wrong setting of the decimal separator key. Can you check this?
Created attachment 136347 [details] wrong decimal separator key for locale German
I cannot confirm your observation. For me cell and formula bar both have a comma as separator, local and document language in German.
I tried again to reproduce it, but I couldn't. So I think this bug occurs under certain circumstances, but it is not really clear how to reproduce it. So i think it's the best to change it back to unconfirmed, until there are clear steps to reproduce it always
Just in case it can be useful info, I am on: * Linux 64 bit * Kubuntu 17.04 with the latest KDE plasma (from the dedicated PPA) * Using the LibO debs from Libreoffice.org (rather than those from my distro) * Using LibO with the KDE integration (VCL: KDE4) * Mixed locale as default on my system (English language with Italian rules for many things) LANG=en_US.utf8 LANGUAGE=en_US LC_CTYPE="en_US.utf8" LC_NUMERIC=it_IT.utf8 LC_TIME=it_IT.utf8 LC_COLLATE=it_IT.utf8 LC_MONETARY=it_IT.utf8 LC_MESSAGES="en_US.utf8" LC_PAPER=it_IT.utf8 LC_NAME=it_IT.utf8 LC_ADDRESS=it_IT.utf8 LC_TELEPHONE=it_IT.utf8 LC_MEASUREMENT=it_IT.utf8 LC_IDENTIFICATION=it_IT.utf8 * Mixed language settings for LibO User interface: English (USA) Locale setting: Italian (Italy) Decimal separator recognized to be , in locale setting
And what happens, if you make everything Italian, so there are no en_US mixing things up?
(In reply to Buovjaga from comment #8) > And what happens, if you make everything Italian, so there are no en_US > mixing things up? Dear Reporter, Could you please answer the question above? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the question is answered
Dear Bug Submitter, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping-20180731
Dear Bug Submitter, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-20180903