fix: French number parsing ambiguity #7966
Merged
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.
Closes #7866
Discussed with Adobe's globalization team and french CLDR contributor. The consensus was that periods are ambiguous. France started to have recommendations against using periods as group separators in 1948, however, it was still taught in schools for a long time. As a result, depending on age or where someone went to school, they may expect it to be the decimal or they may expect it to be the group separator. To get rid of the ambiguity, it was recommended that we remove period as an allowed character and expand the group separator characters to allow all kinds of spaces so that they can easily be typed out on a standard keyboard.
✅ Pull Request Checklist:
📝 Test Instructions:
🧢 Your Project: