Fix position tracking (0,0) coordinates on Android - fix locale when writing decimals #2881
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
🫢 Java's
String::format
uses a default locale when no locale is provided to it. It means that for US/UK locale it used.
as the decimal separator. However, for example forSK
, it used,
-> Qt was unable to parse double with such decimal separator aaaand 💥We will use the common
Locale.US
for writing doubles. A workaround until this bug is released is to change the system language to English 🇬🇧🇺🇸 ... or some other place where they use.
as decimal separatorResolves #2781
See https://developer.android.com/reference/java/util/Locale#default_locale:~:text=Be%20wary%20of%20the%20default%20locale
I checked other occurrences of
String::format
but they look alright.