Language-independent properties

[Takeshi NISHIMURA]

> where would you define idp.logo then?
> If one configures this in system/messages/messages.properties changes
> will be overwritten by the next update.

There is a file messages/messages.properties (not in system/) for language-independent properties and default values for customized messages.

This file is originally empty with the following comments.
> # You can define message properties here to override messages defined in
> # system/messages/ or to add your own messages.

On 2016/11/22 16:59, Lukas Hämmerle wrote:
> Hi Takeshi
>
> On 22.11.16 05:20, Takeshi NISHIMURA wrote:
>> I'm a member for Japanese translation.
>>
>> One suggestion.
>> It seems useful to comment out some properties, which are
>> language-independent (e.g. 'idp.logo' and event/exception to error key
>> mappings).
>> Otherwise, deployers must modify all the property files they deployed to
>> take effect.
>
> Good point. Just yesterday we have been discussing internally at SWITCH
> how to best deploy the translations.
>
> Some strings like the idp.logo will have to be changed by all IdP
> administrators. If one uncomments this value for example in the Japanese
> translation, where would you define idp.logo then?
> If one configures this in system/messages/messages.properties changes
> will be overwritten by the next update.
>
> At SWITCH we are considering to propose in our IdP deployment guide to
> leave the system/messages/messages.properties untouched, install the
> translations in messages/messages_[de|it|fr].properties (like Shibboleth
> recommends it) untouched as well but make the IdP load additional files
> messages/custom_messages_[en|de|it|fr].properties, which contain the
> local changes (e.g. to set logo or IdP name) that not only survive
> updates of the IdP but also updates of the translations.
>
> This will require a one-time change in the Shibboleth configuration though.
>
> Best Regards
> Lukas