M
Matt P
At a multi-language company, many users with different personal language preferences may be working with many different pages in different languages (e.g. updating code examples).
wiki.js should display the UI elements (navigation/controls) to a user based on http
Accept-Language
if the requested language is installed (otherwise site default language).
A user with a login/account should be able to override their
Accept-Language
language preference in their user profile settings to one of the installed languages. Not all users know how to get their browser to change
Accept-Language
header...and they shouldn't need to. For instance a user who has personal language preference (browser
Accept-Language
) of
es
on a wiki that has only installed
de
and
en
with a default
de
can go into their user preferences and select
en
as their preferred UI display language.
A user with language
en
or
en-US
should be able to edit a
de-DE
page on the wiki without the UI controls changing to German...ie edit German language page with English UI controls (or vice versa).
The implication here is that user language for UI internationalization purposes needs to be treated/handled separately from the page content language paradigm.
I understand we want to be able to set
<html lang="XX">
when rendering the pages...however
lang
can be set differently on the content editor/viewer container than it is on the root
html
or
body
tag. So I don't think this should be a problem.
https://developer.mozilla.org/en-US/docs/Web/HTML/Global_attributes/lang
I felt like I already posted about this somewhere but couldn't find it on canny or github...so I don't know. But it comes up often with our users.