Does anyone know how the text of approval forms can be translated?
I don't see here the possibility like in request forms where you can create attributes which can be translated in the custom string file for a specific language.
Any idea?
Does anyone know how the text of approval forms can be translated?
I don't see here the possibility like in request forms where you can create attributes which can be translated in the custom string file for a specific language.
Any idea?
Hi,
also complex but centrally managed: use one javascript file that stores your maps of key:value pairs for each language you want to support. Then have the approval form load that javascript file, have each text represented as a <span> element with its matching ID, interpret the browser language and then supplement each <span> content with its matching value of your language file.
The default language could be English (or whatever the majority of your audience understands). If the email client fails to run the javascript you at least end up with something instead of nothing.
That way you need to only change a translation once (in that javascript file), can easily add any number of languages without further touching the forms.
Be aware that this file would need to be accessible to the email client. If you uploaded the file on the IGL server then likely the email client must either reside inside the corporate network directly or via VPN. Alternatively you could store that file on a public accessible place.
thinking it further, if the user is outside the network, any links provided in the email might not work anyways unless that IGL instance is reachable from everywhere. in that case the JS file will also be accessible.
Frank
Unfortunately there is no way here to do use the localized strings.properties files as an email is sent out to the users without any UI interaction. The way I see it, I see two suggestions: