#904 Exception messages are not being translated on the client side.
Closed: Fixed None Opened 13 years ago by pzuna.

Currently exception messages are translated when the exception is created on the server side.


I know that Jason designed this so that the client did all the translations but would it make sense to send LANG to the server over JSON/XML-RPC and let the server handle the translation?

The browser should send a Languages header and we can use LANG on the ipa client side. If no language is sent default to the current locale I guess.

It turns out that exceptions cannot be easily transferred over XML-RPC in translatable form. It's necessary to have them translated on the server side to the language provided by the client in the 'Accept-Language' HTTP header.

Currently, the IPA client (ipa script) doesn't send any additional headers. We need to modify the Transport classes to do it.

Rob suggested that we pass language in the header as browser does.

fixed with recent series of localization patches from

commit: [changeset:6eb70ea]

to

commit: [changeset:1eb3033]

Metadata Update from @pzuna:
- Issue assigned to pzuna
- Issue set to the milestone: FreeIPA 2.0.3 RC3 (bug fixing)

7 years ago

Login to comment on this ticket.

Metadata