New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Decimal number format changes with language #6
Comments
I'm not able to repro, but you are right that json should not change depending on language + culture. The attached version has made the output culture-invariant, which should yield the needed behavior. I first tried on 0.999. I tried to force:
And then, asking dotnet for --help gives
So the language did change. But then doing an acq and
gives the following: This has the decimal points as periods in spite of being in German on version 0.999. But this might not be a surprise because sometimes you can't switch culture completely. In any case, the outputs should be cultural invariant for 0.9991 if you have time to try. Looks like this release also has correction to phase inversion on inputs. |
Thanks! I tested it and it now works for me with German language, as well as English. |
I got a confirmation that v0.9991 works like it should with German language setup! |
Still curious about whether that negative phase is expected in the new version? |
I received a report from a German user that QA401W isn't displaying anything, but that requests seem to go OK between the browser and QA401H. I was able to reproduce, and it looks like this after doing an acquisition:
There are no errors in the log of QA401H, and no errors in the console or network tab of the developer tools in the browser.
What happens is that if you configure your OS (at least on Linux) to some languages, the number format changes, and QA401H adapts. The browser does not though, so the JSON parser fails to interpret the numbers.
This is how it is normally for me:
Floats use period as the decimal separator.
This is how it looks if I change the language to German:
Suddenly floats use comma as the decimal separator.
I started QA401H like this to reproduce:
It looks like the JSON standard expect floats to use period as the separator:
That also seems consistent with the behaviour the user experienced.
Is it possible to make QA401H return a consistent number format no matter the language?
The text was updated successfully, but these errors were encountered: