<p dir="ltr"><br>
On Oct 8, 2015 6:53 AM, "Stian Thorgersen" <<a href="mailto:sthorger@redhat.com">sthorger@redhat.com</a>> wrote:<br>
><br>
> With regards to internationalization I have two questions:<br>
><br>
> * Should we fallback to English messages if a key is missing in a translation? Alternative is to show key, but that's not going to help anyone</p>
<p dir="ltr">A missing key is a bug and showing the message in the default locale may hide the problem. </p>
<p dir="ltr">Even though showing the key does not help the end user it helps the developer and identifies the problem. For this reason I think showing the key would be a good idea.</p>
<p dir="ltr">> * Should we change message bundles to UTF-8? Or is ISO 8859-1 going to work for all languages?</p>
<p dir="ltr">Depends what those all languages are :-)</p>
<p dir="ltr">I think UTF-8 is the best choice as it will handle practically any character. </p>
<p dir="ltr">But if you're referring to Java resource bundles the encoding for .properties is ISO-8859-1 but there are means to handle any UTF-8 character.</p>
<p dir="ltr">Best regards,<br>
Thomas<br></p>
<p dir="ltr">><br>
> On 7 October 2015 at 18:42, Stan Silvert <<a href="mailto:ssilvert@redhat.com">ssilvert@redhat.com</a>> wrote:<br>
>><br>
>> Marko brought this to my attention yesterday. For some things, we<br>
>> dynamically create UI. In this case, the java code contains the English<br>
>> text and it needs to be localized. Luckily, the solution was pretty<br>
>> straightforward. We just replace the English text with a key into the<br>
>> message bundle. The html template that displays this text already pulls<br>
>> from an Angular scope so we just leave that alone and pass it through<br>
>> the |translate filter. You do need to also add the double-colon.<br>
>><br>
>> One nice side effect is that if the key is not found in the bundle then<br>
>> the output of the translate filter is the unchanged text. This means<br>
>> that any code which has not converted to using bundle keys will still<br>
>> work as expected. And, any third-party providers can just pass in<br>
>> plain text if they don't care about l10n. If they ever do care about<br>
>> l10n we will just need to provide a means for them to add key/value<br>
>> pairs to the resource bundles.<br>
>><br>
>> Here is an example for anyone who needs to localize English text<br>
>> embedded in java:<br>
>> <a href="https://github.com/ssilvert/keycloak/commit/c9437595b70810c4472325373dd8833c37be8549">https://github.com/ssilvert/keycloak/commit/c9437595b70810c4472325373dd8833c37be8549</a><br>
>><br>
>> Stan<br>
>> _______________________________________________<br>
>> keycloak-dev mailing list<br>
>> <a href="mailto:keycloak-dev@lists.jboss.org">keycloak-dev@lists.jboss.org</a><br>
>> <a href="https://lists.jboss.org/mailman/listinfo/keycloak-dev">https://lists.jboss.org/mailman/listinfo/keycloak-dev</a><br>
><br>
><br>
><br>
> _______________________________________________<br>
> keycloak-dev mailing list<br>
> <a href="mailto:keycloak-dev@lists.jboss.org">keycloak-dev@lists.jboss.org</a><br>
> <a href="https://lists.jboss.org/mailman/listinfo/keycloak-dev">https://lists.jboss.org/mailman/listinfo/keycloak-dev</a><br>
</p>