Dutch translation improvements #395
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
Fixes a few minor Dutch typo's.
All options don't end with a "." except one. This looks inconsistent. Fixed.
Klocman
approved these changes
Aug 2, 2022
There was a problem hiding this comment.
Looks good, thank you! Sending a PR like this is the best way to help. You can use ResxResourceTranslator if you didn't already to easily edit the translations on a cloned repository.
|
Thanks @Klocman ! I'll go through the rest of the translation soon with that tool. Thanks for the advice. |
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.
As a translator for WordPress core, meta, theme's and plugins... I wanted to go through other translations. Today I made a few improvements to the Dutch translation of one of my fav programs ever. I want to dive more into the translation but I wonder if this is the only way or if there is another way.
In any case, I hope I fixed it in the right way. :)