-
Notifications
You must be signed in to change notification settings - Fork 4
Revised Swedish translation #597
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: dev
Are you sure you want to change the base?
Conversation
Signed-off-by: Samuel Rinnetmäki <[email protected]>
daniel-mader
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey @samuelmr! Thanks a lot for the contribution! 👍 It looks like you might have worked on a previous version of the translation file. I left some comments where the "technical part" (not your updated translations) of the file seems to be reverted.
| @@ -1,9 +1,9 @@ | |||
| import type { Translation } from '../i18n-types'; | |||
| import type { BaseTranslation } from '../i18n-types'; | |||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We use English as the "base translation", so all other translations should indeed follow the Translation type. This proposed change should be reverted.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Agreed. Our Swedish translator has indeed used the previous translation as the base, which is probably the reason why some things are out of sync with the current code.
Can you fix this, or should I modify the PR? (I probably don't have time this week.)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@samuelmr I don't think I have the permissions to edit this PR directly.
| ONBOARDING: { | ||
| WELCOME: { | ||
| GREETING: 'Välkommen till', | ||
| GREETING: 'Välkommen', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is rendered as "Welcome to UniMe" in the final app in order to greet the user on the first screen. When using only "Välkommen", it would render as "Välkommen UniMe". Is that intended? Or should it stay at "Välkommen till UniMe"?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"Välkommmen till" is the correct translation.
| TITLE: 'Aktivera {type}', | ||
| DESCRIPTION: 'Vill du ställa in {type} för att låsa upp appen?', | ||
| CONFIRM: 'Ja, använd {type}', | ||
| TITLE: 'Aktivera {type:string}', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Defining the data type of the variable is only required when providing a BaseTranslation in the i18n library. These changes should be reverted and indeed stay with {type} only.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same as #597 (comment)?
| }, | ||
| ADD_CREDENTIALS: { | ||
| BUTTON: 'Lägg till', | ||
| NAVBAR_TITLE: 'Lägg till data', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Removing all these fields would leave the translations empty.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is probably unintended.
Description of change
Human-revised version of the previous auto-translation.
Links to any relevant issues
Be sure to reference any related issues by adding
fixes issue #.How the change has been tested
Describe the tests that you ran to verify your changes.
Make sure to provide instructions for the maintainer as well as any relevant configurations.
npm run testDefinition of Done checklist
Add an
xto the boxes that are relevant to your changes.