Skip to content

Conversation

@samuelmr
Copy link
Contributor

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 test

Definition of Done checklist

Add an x to the boxes that are relevant to your changes.

  • I have followed the contribution guidelines for this project
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes

Signed-off-by: Samuel Rinnetmäki <[email protected]>
@samuelmr samuelmr requested a review from daniel-mader as a code owner August 28, 2025 10:53
Copy link
Collaborator

@daniel-mader daniel-mader left a 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';
Copy link
Collaborator

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.

Copy link
Contributor Author

@samuelmr samuelmr Sep 2, 2025

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.)

Copy link
Collaborator

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',
Copy link
Collaborator

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"?

Copy link
Contributor Author

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}',
Copy link
Collaborator

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.

Copy link
Contributor Author

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',
Copy link
Collaborator

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.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is probably unintended.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants