Change hardcode strings in "Pages" to i18n keys #6738
Conversation
This file contains 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
quintushr
reviewed
May 6, 2024
There was a problem hiding this comment.
Added translation support for the label and hint of the features switch, enhancing the user experience.
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.
Changed all hard coded strings in "Pages", "Page Details" and "Visualize".
Is there any way to get access to Wiki JS localization database, to contribute keys?
If so, I would complete changing all hard coded strings on whole project and will contribute on translation in lokalise as Russian translator.
Or if there's another way to help with translation in current 2.x version, please, let me know.