[7.x] Fix some more translation strings#458
Merged
duncanmcclean merged 3 commits intostatamic:masterfrom Nov 19, 2025
Merged
Conversation
duncanmcclean
approved these changes
Nov 19, 2025
Contributor
Author
|
Hi @duncanmcclean, thanks for merging. Isn't |
Member
|
Ah good catch, you're right! 🙈 |
Contributor
Author
|
Maybe just change to |
Member
|
Done in c4fef32 |
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.
Follow up of #454
I found some more strings who could not be translated via the addon's PHP translation files.
Apart from those mentioned in this pull request, there are still others. But they are already covered by Statamic core, so I left them out. For example:
In addition, I have replaced >= with the correct typographical symbol ≥ in the English translation.
If this gets merged, I will update the German translations.