To support this we would have to introduce additional syntax ... For
example rather than calling:
context.form()
.setError(Messages.FEDERATED_IDENTITY_CONFIRM_LINK_MESSAGE,
duplicationInfo.getDuplicateAttributeName(),
duplicationInfo.getDuplicateAttributeValue())
we would have to do something like:
context.form()
.setError(Messages.FEDERATED_IDENTITY_CONFIRM_LINK_MESSAGE, "${" +
duplicationInfo.getDuplicateAttributeName() + "}",
duplicationInfo.getDuplicateAttributeValue())
And adjust localization part to check if value starts with ${ and
first localize the value before passing it as parameter to localize
the message.
On Thu, Jan 14, 2016 at 2:40 PM, Stian Thorgersen <sthorger(a)redhat.com> wrote:
Feel free to create a JIRA issue. The core Keycloak team only
maintains the
English translation. All other translations has to be maintained by
community.
On 14 January 2016 at 14:31, Helder dos S. Alves <helder.jaspion(a)gmail.com>
wrote:
>
> Hi.
>
> The "Account Already Exists" page is not translated correctly.
> The message:
> federatedIdentityConfirmLinkMessage=User with {0} {1} already exists. How
> do you want to continue?
>
> The {0} comes with the property name (email).
> The property name should come translated. Example: "E-mail" in portuguese
> and german, "Courriel" in french.
>
>
> Regards.
>
> Helder S. Alves
>
> _______________________________________________
> keycloak-user mailing list
> keycloak-user(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/keycloak-user
_______________________________________________
keycloak-user mailing list
keycloak-user(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-user