As a Belgian, I can assure you the majority of the internet does not even get that part right. I get websites in the wrong language all the time.
PSA: The majority language in Belgium is not French.
i18nstrings = {'My string':<?= _('My string') ?>, 'Second string':<?= _('Second string') ?>};
then you can just do stuff like elem.innerHTML = i18nstrings['My string'];
Of course, you process the language header in the backend.
I reviewed a couple of i18n libraries for javascript but ended up liking this approach more. It was simple and effective.
In my experience it doesn't work either way, french-speaking walloons get dutch, vlaming get french, and I assume german-speaking walloons get danish or icelandic just to fuck with them, possibly Schwiizertüütsch to taunt them.
> In my experience it doesn't work either way, french-speaking walloons get dutch, vlaming get french, and I assume german-speaking walloons get danish or icelandic just to fuck with them, possibly Schwiizertüütsch to taunt them.
But these words are better than faux IKEA names.
> In my experience it doesn't work either way, français-speaking wallons get vlaams, vlaming get français, and I assume deutschsprachige gemeinschaft get dansk or íslenska just to fuck with them, possibly schwiizertüütsch to taunt them.
The younger generation here really doesn't mind watching originally English content in English, with English subtitles (or just no subtitles at all). Even content that isn't originally English, I'd be fine having audio in the original language and English subtitles. But Netflix won't do that.
If they loosened their language restrictions a bit I am sure I would get sooooo much more content...