Added Czech translation#903
Merged
Merged
Conversation
Owner
|
Thanks, @petrkr , I think using translated names might be better, as you already said. I think that's something we can change easily afterwards if it doesn't fit. How is using the nested keys for you? Makes that sense? Then we could continue with this way and adding more strings. I didn't add more yet, because I want to clarify such things, first :-) |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
I have not so much idea if I have to use "cz_Czech" or translate that "Czech" as I did it..
Since in GUI is visible filename and not language name in some applications in Language selector is Czech, in some "Cestina"
Maybe translated names is better for non-english speaking peoples ? Japanese would be then like
jp_日本語.jsoninstead ofjp_Japanese.json