<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Not directly related, but IMO we can
potentially improve the experience for translators/maintainers and
create some tool, which will simplify their work. This can result
in better experience for them and hence more contributions for
more languages.<br>
<br>
IMO it is currently a bit of pain to maintain the translation and
manually check if there were some recent changes in english file
"messages_en.properties" and then adding/updating them to my
locale (assume it's messages_es.properties) . So I am wondering
that we will have a tool (or maybe we can reuse some already
existing tool), which will:<br>
<br>
- Check the last github revision of my "messages_es.properties"
file. Let's assume this is revision XY<br>
- Then check english locale file "messages_en.properties" and look
for all the commits newer than XY<br>
- The tool will automatically remove all the keys from
"messages_es.properties", which were in the meantime removed from
"messages_en.properties"<br>
- Then tool will create/update the key/value pairs in
"messages_es.properties" for all the keys, which were added or
updated in the meantime in "messages_en.properties" . <br>
<br>
So assume that in messages_en.properties you added the key:<br>
<br>
greetings.key=hello<br>
<br>
then in messages_es.properties, the tool will generate something
like:<br>
<br>
greetings.key=<TRANSLATE_ME> hello<br>
<br>
<br>
So the translator will be just required to check the keys with
<TRANSLATE_ME> and translate them to his language like:<br>
<br>
greetings.key=buenos dias<br>
<br>
Note that translator doesn't need to manually check what was added
or updated in the meantime. He is also not required to
continuously switch between messages_en.properties and
messages_es.properties and compare what is the english translation
for "greetings.key" etc.<br>
<br>
Having separate repositories will be good, on the other hand it
may complicate things if we want to have some tool like I
mentioned above (but maybe not, if it's able to work with times of
commits).<br>
<br>
Marek<br>
<br>
On 06/06/16 08:14, Thomas Raehalme wrote:<br>
</div>
<blockquote
cite="mid:CAPyAMoZdmW82jwo6n4GPqJJPU+pxVM-zDR9wpb1aah1uypJ-yA@mail.gmail.com"
type="cite">
<div dir="ltr">
<p dir="ltr">How about making translations deployable in a
similar way as themes? The base theme would define the
required set of keys which each translation should include.
You could even write tests to make sure the translation is
complete which would simplify maintenance.</p>
<p>Perhaps the main distribution could include only English as
it would now be simple for the admins to deploy the needed
translations. If the translations are separated from the main
Keycloak repository, as you suggested, then the main
repository would not be dependant of up-to-date translations
(which could slow the development down if they start lagging
behind). For the same reason it could also be beneficial to be
able to release translations independently from each other.<br>
</p>
<p dir="ltr">Themes would still need a way to include
custom/override messages but they could be included directly
in the theme just like now.</p>
<p>Just an initial thought....</p>
<p dir="ltr">Best regards,<br>
Thomas </p>
<p dir="ltr"><br>
</p>
<div class="gmail_quote">On Jun 3, 2016 14:34, "Stian
Thorgersen" <<a moz-do-not-send="true"
href="mailto:sthorger@redhat.com" target="_blank">sthorger@redhat.com</a>>
wrote:<br type="attribution">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">We need to find a way to share translations
that scales. We're not able to maintain all these
translations ourselves so I'm considering adding some
external repository for the translations and have elect a
maintainer for each language.
<div><br>
</div>
<div>Does anyone have a good suggestion how to deal with
this?</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On 31 May 2016 at 12:01, Thomas
Raehalme <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:thomas.raehalme@aitiofinland.com"
target="_blank">thomas.raehalme@aitiofinland.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">Hi!
<div><br>
</div>
<div>We need to translate Keycloak user interface
(excluding admin console) to the Swedish language.
I was wondering if anyone has already done the
translation and would be willing to share it?</div>
<div><br>
</div>
<div>We have already translated Keycloak to Finnish
and hope to share the translation with the
community in the near future.</div>
<div><br>
</div>
<div>Best regards,</div>
<div>Thomas</div>
</div>
<br>
_______________________________________________<br>
keycloak-user mailing list<br>
<a moz-do-not-send="true"
href="mailto:keycloak-user@lists.jboss.org"
target="_blank">keycloak-user@lists.jboss.org</a><br>
<a moz-do-not-send="true"
href="https://lists.jboss.org/mailman/listinfo/keycloak-user"
rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/keycloak-user</a><br>
</blockquote>
</div>
<br>
</div>
</blockquote>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
keycloak-user mailing list
<a class="moz-txt-link-abbreviated" href="mailto:keycloak-user@lists.jboss.org">keycloak-user@lists.jboss.org</a>
<a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/keycloak-user">https://lists.jboss.org/mailman/listinfo/keycloak-user</a></pre>
</blockquote>
<br>
</body>
</html>