Dutch translations not working #426
Assignees
Labels
Comments
trieloff
added a commit
that referenced
this issue
May 19, 2022
trieloff
pushed a commit
that referenced
this issue
May 19, 2022
## [7.1.1](v7.1.0...v7.1.1) (2022-05-19) ### Bug Fixes * **i18n:** align Dutch locale name with standard pattern ([d940cd4](d940cd4)), closes [#426](#426) * **i18n:** dutch locale available as command line option ([e8c9304](e8c9304)), closes [#426](#426) * **i18n:** support Dutch locale as command line option ([0c0fbbd](0c0fbbd))
|
🎉 This issue has been resolved in version 7.1.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi @trieloff,
Thank you for merging the Dutch translations. I think I did something wrong. When I choose nl-NL it tells me I can only use en_US and de. I looked at the code where I can add nl-NL but I didn't find it can you add it or tell me where to add. And maybe it is a better idea to call the Dutch translation file also with a underscore like the English one? eg: nl_NL
Expected Behaviour
Using Dutch translations
Actual Behaviour
Argument: l, Given: "nl-NL", Choices: "en_US", "de"Reproduce Scenario (including but not limited to)
/jsonschema2md -l nl-NL -d ./schemas -o ./docs -x -Steps to Reproduce
Create a schema and run the command with -l nl-NL
Platform and Version
All (I think)
Sample Code that illustrates the problem
Argument: l, Given: "nl-NL", Choices: "en_US", "de"The text was updated successfully, but these errors were encountered: