Store interface language for users about v6_api HOT 5 CLOSED

This could be done this way:

• during registration, read the current language of the UI and send it together with other info;
• store it in user table;
• use it for sending emails...
• each time the user change the language a request is sent to the API to update the state.

from v6_api.

And:

• when logging in, the language is sent to the UI so that the interface language can be set accordingly.

from v6_api.

Could this "user prefered language" attribute be used to serve documents when the language is not specified?
For instance in v5, there are links such as http://www.camptocamp.org/summits/37355 that will redirect to http://www.camptocamp.org/summits/37355/fr/mont-blanc depending on the available locales, the UI interface language or some priority list of languages.

Of course for anonymous users we would not have such a "user prefered language" attribute and should use a default lang.

from v6_api.

On the ui server side you usually do not have the authentication token (only when doing xhr requests where the token is explicitly set in the headers).

But the current interface language is stored in a cookie, which is already used for list views, see c2corg/v6_ui#73.

from v6_api.

Can we close this issue @gberaudo ?

from v6_api.