Skip to content

updated NL messages to complete missing translations and improve exist…#38685

Merged
jonkoops merged 3 commits into
keycloak:mainfrom
janher:feature/38614-nl-translations
Apr 23, 2025
Merged

updated NL messages to complete missing translations and improve exist…#38685
jonkoops merged 3 commits into
keycloak:mainfrom
janher:feature/38614-nl-translations

Conversation

@janher

@janher janher commented Apr 4, 2025

Copy link
Copy Markdown
Contributor

updated NL messages to complete missing translations and improve existing translations

Closes #38614

@janher janher requested review from a team as code owners April 4, 2025 10:58
ahus1
ahus1 previously requested changes Apr 4, 2025

@ahus1 ahus1 left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Thank you for the pull request.
Please add a sign-off to your PR as outlined in the CONTRIBUTING.md guide. Then force-push your changes to the PR branch.

@janher janher force-pushed the feature/38614-nl-translations branch from f7f424d to 788105b Compare April 4, 2025 11:07
@ahus1 ahus1 dismissed their stale review April 4, 2025 11:57

Issues addressed

@ahus1

ahus1 commented Apr 4, 2025

Copy link
Copy Markdown
Member

@janher - I pushed one commit as out automatic checks complained: One of the HTML tags was incomplete.

Another things is single quotes ('): They have a special meaning to escape content when used in the backend so you always need to add two of them there, but not in the frontend. See "Handling of single quotes" for a longer explanation.

If you have a working Java/Maven environment, you can run the checks locally using

./mvnw -am -pl js,themes clean install

With the latest commit 502c6144672c47feeabdeb98f271790ec5b9322f this should now be fine and should build.

We now need a review of a second native NL speaker to approve your changes. Maybe @jonkoops has the time to do it, or you ask a friend or colleague to review the changes in the PR. Thanks!

@ahus1 ahus1 self-assigned this Apr 4, 2025

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Here the word 'credential' is used, but before the Dutch variant 'aanmeldgegevens' is used, this should be consistent.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

I agree with you about being consistent.
I believe this line was already in the file, and I just moved it up so the key was in the same place as in the English messages.

I'm actually on the fence which one we should use.

The argument for using "credential", would be that it is closest to the English word. I imagine this message will end up with an administrator sooner or later, and the Admin UI is not available in Dutch (and the administrators that I know, prefer the English UI for managing more technical settings).

When using "aanmeldgegevens", end users can imagine more easily that it is about something they use to sign in, decreasing the chance that administrators will get questions.

I don't think the concept of a credential is presented in the Account UI, The relevant page is called "signing in" ("aanmelden").

All in all, I have a slight preference for "aanmeldgegevens", what do you prefer?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

My preference would also be 'aanmeldgegevens', so let's go with that 👍

@jonkoops jonkoops left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

LGTM, let's handle #38685 (comment) as a possible follow up

@jonkoops jonkoops enabled auto-merge (squash) April 23, 2025 15:15
@ahus1 ahus1 force-pushed the feature/38614-nl-translations branch from 30d3119 to 24beb05 Compare April 23, 2025 15:42
janher and others added 3 commits April 23, 2025 22:03
…ing translations

Closes keycloak#38614

Signed-off-by: Jan Herrygers <jherrygers@vaa.com>
Closes keycloak#38614

Signed-off-by: Alexander Schwartz <aschwart@redhat.com>
Closes 38614

Signed-off-by: Jan Herrygers <jherrygers@vaa.com>
@ahus1 ahus1 force-pushed the feature/38614-nl-translations branch from 24beb05 to 8f63d88 Compare April 23, 2025 20:03
@jonkoops jonkoops merged commit efcd6aa into keycloak:main Apr 23, 2025
@ahus1

ahus1 commented Apr 23, 2025

Copy link
Copy Markdown
Member

@janher - with this PR merged, you are now ready to do perform the next updates in the Weblate UI directly.
Welcome on board!

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

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Improve Dutch translation for Theme base/login and base/email

4 participants