Translating messages in a non-neutral language

[bdovaz]

According to the documentation it is parsed in messages_{locale}.properties format.

In my theme.properties I have it defined like this according to #36859 (comment):

locales=en-US,en-US,en-ES,en-MX

This works fine for example for messages_es.properties but not for messages_es-ES.properties or messages_es-MX.properties.

It's like it doesn't find them, is it a bug?

[danielFesenmeyer]

Have you enabled internationalization on the realm and also defined the available languages on realm level? (You can do that with the Admin UI, on the "Internationalization" tab.)

[bdovaz]

Obviously, as I said, it works for neutral languages. If internationalization were not enabled, it wouldn't even work for those.

[danielFesenmeyer]

@bdovaz I think your files should be called messages_es*_*ES.properties and messages_es*_*MX.properties.
Don't know why, but that's the same pattern as used for the keycloak internal pt-BR translation file: https://github.com/keycloak/keycloak/blob/main/themes/src/main/resources-community/theme/base/login/messages/messages_pt_BR.properties

[bdovaz]

Thank you very much, I've been able to test it and that's how it is.

I think the documentation should be modified to reflect this observation. Because in Java, locales use “-”, not “_”.