remove workaround for translation formatting#491
Merged
Conversation
eb5ee76 to
5a06c90
Compare
aduffeck
reviewed
Mar 26, 2025
5a77a78 to
2113112
Compare
fccfa87 to
ddada9a
Compare
Signed-off-by: Christian Richter <[email protected]>
76ce8f2 to
7227a1e
Compare
Signed-off-by: Christian Richter <[email protected]>
7227a1e to
17b1c71
Compare
micbar
approved these changes
Mar 26, 2025
This was referenced Mar 26, 2025
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
3 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.
We have removed a workaround for
github.com/leonelquinteros/gotext v1.7.0that required an additional parameter tot.Get()for properly formatting translations. This has been rendered obsolete with the bump to1.7.1