Improve dutch #539
Merged
Improve dutch #539
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
|
The test will currently fail because the main branch I forked from has a failing test. See #538 |
wanasit
reviewed
Nov 19, 2023
wanasit
reviewed
Nov 19, 2023
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.
Correct in Dutch is "komend uur", not "komende uur".
And there are some other combinations that were not detected yet: "aankomende maand", "komend jaar" and some more.
In this PR both
"komend" and "komende",
"volgend" and "volgende",
"vorig" and "vorige",
"aankomend" and "aankomende"
are allowed.
Changed test for "volgende maand" into "aankomende maand", as there are already tests for "volgende week", "volgende dag", "volgend jaar" and no tests for "aankomende".