Can you briefly describe how it works?
With regards to repository and commits we can't use anything that commits
directly to the repository. We need something where updates to a single
language can be batched and sent as a PR with a single commit.
On Tue, 5 Feb 2019 at 09:46, Eugen Stan <ieugen(a)netdava.com> wrote:
Weblate can wrok with the respository as is but it can introduce a lot
of noise for the commits related to translation. That is why we chose to
split the translations into another module.
In our case we have quite a few languages and a lot of text to be
translated so there is a lot of noise commming as git commits from
In keycloak I believe this will not matter that much since it has less
text to be translated.
Weblate has the feature to implement translators + reviewers processes.
It can also work with offline translation.
We had a very good experience with it so far. Michal (the creator of
weblate) has proven very responsive and helpful even when we did not pay
for maintenance. In our case we ended up paying for maintenance because
it is worth it.
For keycloak we have the following languages translated for all
components (except Admin) with professional translators or local people:
Arabic, Dutch, English Australia, English UK, Latvian, Lithuanian,
Norwegian, Romanian, Russian, Spanish, Swedish, Vietnamese and more are
I think the setup can be done in a day or so.
La 05.02.2019 08:16, Stian Thorgersen a scris:
> I'm afraid using sub modules is not an option for us.
> I'm open to a tool to aid with translation, but we would need to
> review what tools are available before selecting one. The tool would
> have to be free for Open Source projects and self-hosting is not an
> option. It would also have to work with the repository as is and not
> require changes to where and how the translations are maintained.
> On Mon, 4 Feb 2019 at 14:41, Eugen Stan <ieugen(a)netdava.com
> <mailto:firstname.lastname@example.org>> wrote:
> Hello again. We managed to translate some languages already and we
> like to contribute the translations upstream and hopefully improve
> translation process.
> We have some feedback from our process. We use this process
> and the idea is to have it working for keycloak open source
> Proposal for Keycloak
> - We propose to move the community translations in a separate git
> project - just with the translations
> - That repository is going to be used by Weblate as a source of
> translations ( use Free Hosted Weblate -
> - The translations project can be added as a git sub module to the
> keycloak project
> - during build the translations can be copied to the final artifact
> We do this allready and we can help with the code migrations. Having
> this setup will improve the contributions to translations and also
> ability to change the translations easily.
> La 01.12.2018 19:22, Eugen Stan a scris:
> > Hello,
> > Where can we find the translation files for Keycloak and what is
> > process for upstreaming them?
> > We are planning to deploy Keycloak for authentication for our
> > We have users all accross the globe and we have translators that
> we can
> > ask to translate.
> > I'm planning to push the translations upstream once they are
> done (need
> > to get approbal on this).
> > Regards,
> > Eugen
> keycloak-dev mailing list
> keycloak-dev(a)lists.jboss.org <mailto:email@example.com>