Repository navigation
fix(client): match lean-i18n escaping in translation keys - #563
Merged
TentativeConvert merged 1 commit intoOct 2, 2026
Merged
TentativeConvert merged 1 commit into
TentativeConvert merged 1 commit into
Conversation
TentativeConvert
merged commit Oct 2, 2026
eb7977d
into
leanprover-community:main
0 of 4 checks passed
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.
NNG4’s German translation uses
§placeholder keys. For text containing backslashes, lean-i18n doubles them when creating the key, but Lean4Game’s lookup did not. This made documentation such as theexacttactic card fall back to English.Related to #411 and leanprover-community/NNG4#162