from what I understand, changing the interface language when using the Multiuser plugin is disallowed by default as hanging the language would change it for everybody.
Ideally this would be a per-user setting, stored in the user's browser, as currently we have some Russian and English proxies, which people in other countries aren't able to use due to the language being stuck as the region default.
Making it per-user and allowing it to be changed by default with the Multiuser proxy would solve this problem.
Additionally, if no language has been set by the user, it would be nice to respect the Accept-Language HTTP header if it matches one of ZsroNet's supported languages.
I would actually propose something more drastic, which I will create an issue on soon.
Unfortunately it's not possible with the current way we handle translations, but when migrating to Python 3 I will try to find a way for this, but it could have some performance drawback
@HelloZeroNet perhaps all translated versions of a site could be rendered if the proxy runner opts into allowing multiple languages, and then one of them would be shown according to what the user's browser has requested?
My website looks at the language field from serverInfo. I'm not sure how that would work with what you want to eventually do.
The site translation based on user setting should be fine, the messages that are in the source code is the problematic part
Well, I was just thinking that the language field from serverInfo is gotten from the server, hence why it's in there. But if you change it to be based on user settings, then shouldn't it be moved elsewhere? Perhaps not, But if so, it would mean zites would have to change to accommodate that.
I made an issue on the more drastic proposal I was talking about earlier: #1460
This is a little related, but may not necessarily be involved with it.