Dear All,
Let me duplicate myself.
I've expected to see messages in Russian at freeipa web login page. File LoginScreen.js contains '@i18n:' prefixes for messages and corresponding translatable text is in mo file already.
That's good. My Accept-Language is 'ru'. But ... all (on this widget) is still in default English.
As i understand JSON-RPC is not available without IPA authorization by design and therefore i18n_messages too.
Which approach can be applied to fix translations? Any ideas?
Your help is greatly appreciated. Thank you.
On ke, 23 touko 2018, Levin Stanislav via FreeIPA-users wrote:
Dear All,
Let me duplicate myself.
I've expected to see messages in Russian at freeipa web login page. File LoginScreen.js contains '@i18n:' prefixes for messages and corresponding translatable text is in mo file already.
That's good. My Accept-Language is 'ru'. But ... all (on this widget) is still in default English.
As i understand JSON-RPC is not available without IPA authorization by design and therefore i18n_messages too.
Which approach can be applied to fix translations? Any ideas?
The only option I see is to introduce another end-point in ipaserver/rpcserver.py that is not authenticated and explicitly serve i18n_messages from it. Since this is a re-design, I'm afraid we'll be unable to do it in 4.7.0.
freeipa-users@lists.fedorahosted.org