I'd also like to +1 for Weblate, it seems to match our open-source philosophy.

Very nice!

The coding TODOs are now done. Keycloak is now also approved for the libre projects hosting.

Tasks that are still ongoing:

• Cleanup of existing translation files: Sometime keys have been renamed in the source files, but not in the translation files.
• Weblate doesn't support the _zero suffix used by i18next translations. This is a known issue, and it is not clear when / how this will be supported, and what a good workaround can could be for this: Weblate removes _zero postfixed keys from translation files that were touched WeblateOrg/weblate#9358

I think we can work around the _zero problem by simply not using those kinds of features. We'll just have to work around these issues until they are fixed. Let me know if I can assist with anything.

I think once we have the system in place we should formalize some kind of process for community translations. I'd like to have designated maintainers for each language that is supported. And we should likely also add a call to action on the site, blog and contributing documentation.

Update on this, we no longer need to worry about the _zero suffix, as the Admin and Account consoles have now been ported over to property files.

Thank you for this update. I've updated Weblate with the new files, and also restricted the languages to NL and DE - the languages between the two of use we are familiar with.

I've created one more PR for a cleanup before I switch Weblate to Keycloak's main repository:

• Cleanup translations for DE/EN for a first test run of Weblate #25450

Once we're happy with the process, we can then add more languages.

PRs have been merged.

Ah got it, sorry wasn't aware of this conversation. I have no objections against this approach, I'll re-open the PR.

@ahus1 Shouldnt it be better if I would first translate files on weblate, which would push files to github and to enable them in *.properties files only after?

I suppose we're are talking about the same thing still things get lost when writing them down. As there are multiple *.properties files, let's try to be more specific:

Let me try again:

• Weblate needs an empty file messages_ka.properties to start with / show the language in the Weblate UI. So adding those empty files is the first PR to the main repository.
• Once you translate in Weblate, it will create one or more PRs with your translations to the main Keycloak repository, and the files will grow.
• Once the translation is complete, there will be another PR to the main repository for the themes.properties files, so that Keycloak will actually serve those translations in the UI. You can (and probably should) have done this change locally before to verify the translations

Are we in agreement?

Got it. Any way to remove/revert last commit (adding ",ka" in theme.properties fle), please?

If you are using the web frontend of GitHub, this might be tricky. I'm helping out here and pushed some changes to the PR. Let's continue the discussion over there.

Weblate is not ready as of yet, if you wish to contribute you can open up a PR instead.

@moritz89 - The Weblate process is now live for the German translation. See https://github.com/keycloak/keycloak/blob/main/docs/translation.md to get started! @robson90 volunteered to take the lead for the German language, so please contact him with any questions you might have.

Happy to see you volunteering! AFAIK you've been contributing to the Arabic translation in the past. Is there a second native speaker you can team up to review your translations?

When I add Arabic to Weblate, the first thing Weblate will do is to removing all message keys from the messages_ar.properties files it assumes to be outdated as the don't exist in the message_en.properties. Once this happens, the first task is to review those removals and check if there was just a change in the key in message_en.properties and the translation can be saved by re-adding it to Weblate with the new key.

Happy to see you volunteering! AFAIK you've been contributing to the Arabic translation in the past. Is there a second native speaker you can team up to review your translations?

cc @Mouhand-Kaddo @alfayez91 if someone interested.

@Eng-Fouad - if you don't find volunteer here, maybe reach out to the Keycloak mailing list and see if someone wants to join.

@GioviQ - in Keycloak's translations - either by file or by Weblate, in all cases where you want to show a single ' in the UI, you will need to put a double '' in the translation. This is due to the Java Messageformat, where single quotes have a special meaning.

See "Within a String, a pair of single quotes can be used to quote any arbitrary characters except single quotes. ... " in the docs for the MessageFormat. I suppose we should add that to the translation guide: https://docs.oracle.com/javase/8/docs/api/java/text/MessageFormat.html

You mean in general or for a specific key?

Weblate will accept both. I did it always similar to the English language.

I have seen already translated strigs with single or double ' , so I was not sure whether both were correct.

If there is a single quote without a matching single quote later, the Message format will show the quote. Once there is a matching quote, then none of the quotes will be shown. It is not very intuitive. I'll see that I add an automatic check to Keycloak. Unfortunately this will only catch those situations after the translation has already been done in Weblate. I'm now going through the Italian translations.

The original idea was to escape placeholders, so '{0}' would print {0} and not replace the placeholder. Well, it turned out to be not a good idea to use a single quote for escaping...

Consider https://graphicdesign.stackexchange.com/questions/66809/what-s-the-right-character-for-an-apostrophe too

@GioviQ - yes, that's a good idea. That should work in the UIs, and I assume in emails as well.

I've created an issue to update the translation file, and also to add a validation in the build. #37931

What you can do today: You can create a pull request to update the messages_it.properties, and then find another Italian native speaker to approve that PR.

What we can do when two Italian native speakers commit to be maintainers of the Italian language: We can setup up Weblate.

I made a PR just to test the process and now I see this PR was not so easy, just like other PRs. But I learnt the "sign off" is just some sort of disclaimer in a commit and if I manually add a line in message like Signed-off-by: GioviQ <my@email> it is the same as using -s option. I discovered now every theme has its own message_{locale}.properties, so one should made the same update to all and that is not efficient. Also managing the project with Visual Studio has some issue and still I don't find a free tool to manage all the message_{locale}.properties at the same time.

The two previous language maintainers weren't able to review the translations, so we were in the process of removing it. The translation.md file is now updated.

We're looking for two new languages maintainers that are active on GitHub and Weblate. In the meantime, we'll be accepting pull requests to those translation files in the Keycloak repository directly.

We're looking for new French language maintainers who would be willing to use Weblate to keep the translation up to date.
Looking at previous PRs to the files, I see that @reda-alaoui as active, as well as @DevRebs and @jmorille.

I you or someone you know would be willing to contribute as described in translation.md, please comment here.

I am willing to contribute. But I'd need instructions and proper access.

@blackholegalaxy - that's great to hear. You can already sign up have a look at the existing translations here: https://hosted.weblate.org/projects/keycloak/#languages

About the process: Please see "Tasks of the language maintainers" for the role description in the translation.md file.

Once there is a second volunteer for the French language, we'll set up French in Weblate and expand the permissions for you and the second volunteer.

Ok will wait for a second partner then :)

@Ecron & @jmallach I added you guys to Weblate. I think we have to wait for this PR to see changes from Weblate to the upstream project.

Weblate create a cleanup PR for CA and removed two items that are no longer available in the upstream #33361.

So I'd say we are all set up, and you can check if everything looks alright in Weblate.

Will do ASAP! cc @Ecron

If an export of weblate resulted in that PR, I'd say we're all set, as there are no changes other than those two strings.

Should we be listed as admins for Catalan or something like that? I don't see anything like that in Weblate. 🤔

@jmallach & @Ecron
I dont know why, but you were removed from the Userslist. I readded you two.

I would appreciated if you extend this https://github.com/keycloak/keycloak/blob/main/docs/translation.md with language and your two names/profile links. Please see the other entries.

As far as I know you are not shown as admins for that specific language. You will be listed, when the first translations are merged.

If anything is unclear just hit me up :)

@y-tabata - I've added @tnorimat as a new Japanese language maintainer. You now should also be a team administrator so you should be able to add and remove team members.

@tnorimat - welcome to Weblate!

@ahus1 Could you add @k-tamura as the new Japanese language maintainer? @k-tamura 's Weblate username is k-tamura.
Or can I, a team administrator, add a language maintainer? I looked at the documentation, but I couldn't really understand what a team administrator can do.
https://docs.weblate.org/en/latest/admin/access.html#team-administrators

@y-tabata what are you trying to achieve ?
Should he replace you ?
Do you want a third Japanese maintainer ?

@robson90 This is to add a fourth Japanese language maintainer and speed up approval of translations.

OK, @k-tamura is now also a team member for Japanese in Weblate. @y-tabata - can you please create a PR to add him to the translation.md file? Thanks!

Sorry for the slow reply. I had a look at the administration of Weblate, and it seems that I missed to add the permission to "review strings" to the admins of each language.

I have now fixed that, again sorry for missing it earlier.

You should now have an additional radio box with "Review state" where you can change a translation to "Approved" (see screenshot below).

In the "Tools" menu, is also the option to bulk-edit translations and change their status. Use it with caution.

Welcome! Let's wait for a second person to join for this task.

@edwint88 - the functionality you ask for doesn't exist, at least not at the moment. I agree it would be great to have such functionality. I suggest to open an enhancement issue on GitHub describing your needs, and then link it from this discussion so people can join in. We can then discuss how a technical solution could look like.

For the time being, looking at the source code might be the way for some of the cases. See for example this file in the login v2 theme with its msg("...") elements referencing the keys found in Weblate: https://github.com/keycloak/keycloak/blob/main/themes/src/main/resources/theme/keycloak.v2/login/delete-account-confirm.ftl

I would be eager to know how other projects approach this.

See screenshot feature in https://docs.weblate.org/en/latest/admin/translating.html#visual-context-for-strings

This will be amazing if we could use this feature.

AFAIK I don't think we have a process generates screenshots of a lot of screen automatically (cc: @jonkoops). I read that Weblate could OCR the screens, and thereby connect it to the keys automatically?

Note that I expect some false positives, as well only a 80% solution as for example help texts usually don't show in screenshots. I'm still curious to see how good we can get it.

I'm happy to provide permissions to someone who wants to evaluate this feature by uploading some first example screenshots.

No, we don't have any sort of automated tooling for taking screenshots. I also don't think that is the way to go, as it would require significant investment and maintenance.

Ideally, keys for localization would have some manner of adding metadata with a description of the key and what the purpose of it is to provide context. For example, GNU gettext PO Files support comments for translators.

According to our process, we would need a second volunteer for Czech. Once we have found that person, we can add Czech to Weblate.
See https://github.com/keycloak/keycloak/blob/main/docs/translation.md#steps-to-add-a-new-language-to-weblate for the process. Maybe you can advertise at work or on the Keycloak mailing list to find a volunteer.

Hi @ahus1 Im interested to do the translation. Here is my account https://hosted.weblate.org/user/martin.kluska/

I also volunteer for the Czech language - https://hosted.weblate.org/user/pschiffe/

@pionl / @pschiffe - Thank you for volunteering! You are now set up in Weblate and can now contribute translations.

Weblate is doing some infrastructure maintenance this weekend (weblate-status-bot/status#1739) but it should be available again on Monday.

@robson90 - please add the new translators and the Czech language to the translation.md file. Thanks!

Hi,

My username on Weblate is rafaelrddc.

Hi, my Weblate username is julianorodrigov.

Hey guys, thanks for volunteering ! Invites should be sent. Happy translating !

@felipebz / @rafaelrddc / @julianorodrigox - Welcome to Weblate! Please make your self familiar with the Weblate web frontend. Please raise any questions you might have here in the discussion, or contact @robson90 or me directly.

When you have the time, it would be great if you would review the existing Portuguese (Brazil) translations and mark them "approved" over the next weeks or so, so they show up in the overview as dark green. Having translations reviewed helps us to have high-quality translations in Keycloak.

Thanks!

Some links that might help:

• Overview of the pt_PR translation: https://hosted.weblate.org/projects/keycloak/-/pt_BR/
• Filtering all pt_PR translations in status translated, but not approved yet: https://hosted.weblate.org/translate/keycloak/-/pt_BR/?q=state%3A%3Dtranslated&sort_by=-priority%2Cposition&checksum=

Hello everyone!

I created a MR by adding the Portuguese (Brazil) information to the 'docs/translation.md' file.

https://github.com/keycloak/keycloak/pull/38997/files

Hey @jmorille & @blackholegalaxy thanks for volunteering ! You should have an invite for Weblate by now.
I will add you guys to the docs/translation.md today or tomorrow.

I can also help for french translation if needed: https://hosted.weblate.org/user/romain/

@Romain7495 - thanks to the two volunteers, French is now on Weblate. Everyone can now contribute to the French translation, while the language maintainers take the extra responsibility to review the community contributes translations.

Please start contributing translations - no additional permission is necessary. If you like the process and want to contribute more, please ping @jmorille and @blackholegalaxy to join the team of language maintainers to also be part of the review process.

@jmorille @blackholegalaxy I translated most the remaining keys in French on Weblate during the past few weeks. Could you review it when you will have the time ?

After contacting @Dodouce and @GitSpoon, I'm happy that they will join the French translation team. They are already familiar with Weblate as they contributed to the French translation in the past.

@robson90 - can you please update the translation.md file? I didn't year back from @jmorille @blackholegalaxy in #42785, so please remove them from the file for the time being until they want to join as language maintainers again.

keycloak-admin-ui-tr.zip
Hello @ahus1 ,
I haven't been able to upload the "keycloak-admin-ui-tr.properties" file via Weblate despite several attempts. The only remaining translation component is "admin-ui".
Could you please upload the attached translation file on your end?

Sorry for the confusion — it seems the upload actually went through on Weblate. I just saw the message:
"Processed 3578 strings from the uploaded files (skipped: 30, not found: 0, updated: 3548)."
So everything looks good now!

Right now, I can see that the translation is 100% complete!

@ariferol sounds great ! Thanks for sharing. Just for clarification, on how you uploaded the properties file:
You clicked on the respective component -> Files -> Upload translation ?

Yes, exactly. I clicked on the specific component, then went to Files -> Upload translation and selected the properties file from there. The upload process took a bit longer than expected, but it was completed successfully.

There had been an unfortunate conflict on Friday where not all changes in Weblate were merged to the main Keycloak repository. I'm sorry that this happend. Due to the conflict I had to reset the state in Weblate with the translations that were merged. Unfortunately this reset some of the translations that were performed during that day.

I'm still analyzing why this happened. The translations are still available both in the translation memory and in the history. Maybe you can go through them and revert them.

For the future, I'll see that I do timely merged of the changes to the main repository.

Again, I'm sorry that this happened.