I'm using version 0.18 of PowerToys and I'm talking about the integrated calculator in PowerToys Run here:
In the german area, we use the comma and not the period as a decimal-delimiter. The current version of the calculator in PowerToys Run only accepts periods as decimal-delimiter. Please add support for the comma and auto-detect Windows settings for regional format, as the Windows regional format has a setting for this.
Thank you!
Great catch!
Even though I hate the fact that these differences exist in the first place, I agree that it should be easy to implement by checking the Regional settings in Windows.
Edit: this method should be default.
Agreed and totally fair feedback.
Please also support the thousands separator (for example 12,345 instead of just 12345) This will help when you copy and paste from other content such as web sites or Excel spreadsheets as numbers are often formatted this way. Of course, the thousands separator characters should be determined using the locale settings in Windows (so , for countries like US and . for some European countries)
Yup, marking it a .20 work item. (2 releases from now)
Please develop this :o)
The total displayed is crazy :
8 . 43*2 = 16 , 86
it does not matter but with the clipboard, it's difficult to work.
The output should be your localized versions for numbers.
The output should be your localized versions for numbers.
The output is localized, as you say, but the input doesn't seem to work in 0.23.2 yet.
Also, is #2265 still on the radar?
In last version when I'm writing this, 0.25.0, the output of the calculation is correctly localized, but the input is not, you're forced to use the C locale decimal delimiter (a dot)
The problem is the parser. That itself isn't and we are using a 3rd party library for that. The calculator team is working on doing a parser as well that is my hope we can leverage.
Even though I hate the fact that these differences exist in the first place
Don't. The world is the way it is.
moving this to https://github.com/microsoft/PowerToys/issues/2265. Once we get the calc engine, localization support will be part of the requirement.
Most helpful comment
The problem is the parser. That itself isn't and we are using a 3rd party library for that. The calculator team is working on doing a parser as well that is my hope we can leverage.