Removed usage of culture-sensitive string operations #1054
Merged
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
…riant culture alternatives
…t()` Fixed translations to map to correct JS functions
exyi
approved these changes
Jun 17, 2021
Co-authored-by: Stanislav Lukeš <exyi@outlook.cz>
|
Yes, I also think that this should be included in 3.1 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Resolves #950. This PR changes all occurrences of
.ToUpper()and.ToLower()to their culture-invariant alternatives. I also fixed JS translations and introduced two new:Changed translations:
string.ToLower()maps toString.prototype.toLocaleLowerCase()string.ToUpper()maps toString.prototype.toLocaleUpperCase()New translations:
string.ToLowerInvariant()maps toString.prototype.toLowerCase()string.ToUpperInvariant()maps toString.prototype.toUpperCase()