This repository has been archived by the owner on Feb 10, 2022. It is now read-only.
Ink Recognizer - Set US Culture to get correct decimal separator #94
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Depending on your culture you might get a comma (,) as a decimal separator. This breaks the request to the API. By making use of a fixed culture the comma separator will be point (.)
sammydeprez
changed the title
CarlosP-MS
approved these changes
Dec 12, 2019
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
The Ink Recognizer is throwing errors when your local culture does not have the '.' point as a decimal seperator. Json polygon data looks like this then:
12,1234566,34,567890
Which is not valid for the API, it needs to be
12.1234566,34.567890
This can be fixed by setting a US culture.