fix: not showing localised strings using Chrome #1021
Closed
Conversation
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
* Resolves #831 Fixing not showing localised strings using Chrome by adding internationalisation tags to `templates/viewer.php` according to the conventional approach in NC to localise apps. Co-authored-by: Oleksa <[email protected]> Signed-off-by: Ferdinand Thiessen <[email protected]>
skjnldsv
approved these changes
Aug 22, 2024
Contributor
Author
|
Lets go with the easier fix: #1022 |
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.
Fixing not showing localized strings using Chrome by adding internationalization tags to
templates/viewer.phpaccording to the conventional approach in NC to localize apps.