Fix nested translations on Windows not recognized - #684
Open
LaurinStapf wants to merge 1 commit into
Open
Conversation
LaurinStapf
marked this pull request as ready for review
July 27, 2026 19:15
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
1 participant
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.
Problem
Nested translation keys e.g.
__('app/test.label')are displayed as "not found" on Windows, even though the translation exists. This is caused by the translation resolution logic not normalizing Windows (\) and Unix (/) path separators when handling nested keys.Fix
Normalize file paths to use forward slashes consistently across all platforms during translation key resolution.