4 ms·
Yeah, the weirdest thing is that HTTP Accept-Language has been around for decades and is usually configured correctly (to the OS system language). No idea why p
by skrebbel 10y ago
Yeah, the weirdest thing is that HTTP Accept-Language has been around for decades and is usually configured correctly (to the OS system language). No idea why people use geolocation for language at all, on the web.
- nkristoffersen 10y agoLocalization is easy with javascript. Just look at navigator.language or navigator.languages[0]
- aclsid 10y agoAnd I suggest following gettext's lead in this regard, so that on your code you would have something like: 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.
- pjc50 10y agoPeople in English-speaking countries are really bad at thinking about localisation since they're not exposed to these issues personally.
- gcp 10y agoBetter hope the Chinese don't take over our economy any time soon, I'm sure their devs have the same view on this.