Make Dutch translation consistent, fix Dutch language errors, and make it real Dutch #1316
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.
https://www.microsoft.com/en-us/language/Search?&searchTerm=number&langID=Dutch&Source=true&productid=All%20Products translates "string" to "tekenreeks", but that is
hypercorrect. Nobody uses that term. In Dutch, we just use the English term "string" colloquially.
prelude to a list of "implications" that have failed. A better English form would be "Failed implications:", and the new Dutch translation expresses that. Furthermore, the wordt "implications",
in English, as well as in Dutch, is extremely confusing here. It is only people who know the Yargs API that understand that these are the dependencies created by the
implies()
method.Users of the CLI have no idea what we are talking about. Yet, until a better form is found in English, it is also kept in Dutch.
config
), the translation should do so too. It was "configuratiebestand", which is Dutch for "configuration file".