As usual, i'm a few steps behind.
On 2/24/2015 8:53 AM, Stian Thorgersen wrote:
+1000
Exactly what I've proposed about 10 times already ;)
----- Original Message -----
> From: "Bill Burke" <bburke(a)redhat.com>
> To: keycloak-dev(a)lists.jboss.org
> Sent: Tuesday, February 24, 2015 2:44:14 PM
> Subject: [keycloak-dev] Internationalization for model data
>
> There's data stored in a bunch of places that should be
> internationalized. i.e. Role descriptions. I was thinking for this
> type of stuff, for both simplicity and ease of migration, we still
> continue to input this type of metadata through one field. Then if the
> user wants to internationalize a piece of data, they just replace the
> text with a property variable.
>
> Role Description: "Admin access to main application"
>
> could be replaced with
>
> Role Description: "${role.admin.description}"
>
> Then the variable 'role.admin.description' is just replaced with a
> theme-based property.
>
> This way, users dont' have to learn about internationalization until
> when and if the need it, existing deployments will still just work, and
> we don't have to expand our data model.
>
> --
> Bill Burke
> JBoss, a division of Red Hat
>
http://bill.burkecentral.com
> _______________________________________________
> keycloak-dev mailing list
> keycloak-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/keycloak-dev
>