New translations keys #48
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
victorbalssa
approved these changes
Nov 8, 2022
|
Also updated them in #55 |
This was referenced Dec 27, 2022
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.
name: Pull request
about: Translations
title: FEATURE_
labels: enhancement
assignees: victorbalssa
Is your feature request related to a problem? Please describe.
This PR is an update of #42, adding new keys to translation and implementing those into the app.
Describe the solution you'd like
Create new keys for
en-UStranslation and implement these across the app, usingtranslatefunction, create before.Describe alternatives you've considered
Use fixed texts in English.
Additional context
At previous PR, I don't see some fixed texts on screen. So, they weren't translated and the internationalization it was incomplete.