Bug 152886 - Setting:"Use english function names" changes valid decimal separator to dot despite set different in local settings
Summary: Setting:"Use english function names" changes valid decimal separator to dot d...
Status: RESOLVED DUPLICATE of bug 151886
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
7.4.3.2 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-01-05 01:17 UTC by e688497
Modified: 2023-01-05 01:57 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description e688497 2023-01-05 01:17:31 UTC
Description:
Since this version the "Use english function names" settings changes the decimal separator to dot despite set different in local settings.






This should not be happening. Decimal separator should be set with local settings and english function names should have no impact on the separator 



Steps to Reproduce:
- Set local settings to any language that uses , as decimal separator. 

- Add formula  =1,1+1 and formula =1.1+1 to the sheet.

- First formular works, second doesn't as it should be.

- Now set the setting "Use english function names" under Libre Calc -> Formula and observe the calculated formular change. 

- The , formula throws a #name error now while the . formula gets calculated now.

Actual Results:
The "Use english function names" setting changes the valid decimal separator

Expected Results:
The "Use english function names" setting should NOT change the valid decimal separator


Reproducible: Always


User Profile Reset: No

Additional Info:
Version: 7.4.2.3 (x64) / LibreOffice Community
Build ID: 382eef1f22670f7f4118c8c2dd222ec7ad009daf
CPU threads: 12; OS: Windows 10.0 Build 19042; UI render: default; VCL: win
Locale: de-DE (de_DE); UI: en-US
Calc: CL
Comment 1 m_a_riosv 2023-01-05 01:57:08 UTC

*** This bug has been marked as a duplicate of bug 151886 ***