refactor(messages.properties): Non alphanumeric character vs special character #62
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
Aaron-Ritter
changed the title
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.
This addresses the Non-alphanumeric character vs special character mentioned in:
FusionAuth/fusionauth-issues#2251
When I was translating to German I thought
password-alpha-constraint=Must contain at least one non-alphanumeric characteris a bit to complex and the use ofspecial characterwould make more sense.When researching German and other languages I was able to find exact results and I am convinced the use of "special character" is more to the point comparing to "non-alphanumeric". In this PR I've translated what I was able to confirm online the rest I left untouched.