i18n: updated locales to reflect latest strings #2989
Merged
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
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.
Description
We often release new features with only
en-USlocale support. Few of such features we released last week was Tabs, Workspaces etc with no full i18n coverage.In this PR, I've added the remaining locales with reference strings from
en-US, and other i18n strings to ensure full coverage of all text displayed in the application.Additional Information
At Hoppscotch, i18n is still a manual, time-consuming, copy-paste effort. This can be changed. This can be automated. @thetronjohnson, can you look into how we can ensure and impose full i18n coverage for every release?