I'll try to expand this over the weekend. Need to describe the problem at the moment that even if you get the localized name, the application won't be localized. The navigator.language is the navigator language, so the application has no way of knowing (currently) that the system language has changed. This would require a change to how the web platform interfaces with the OS to get the user's language. This has privacy issues, as it helps narrow down a user's geographic location down to a country. The HTML5 spec currently tries to protect users from this by telling the UA to always report "en-US".
Reviewed. LGTM.
I'll try to expand this over the weekend. Need to describe the problem at the moment that even if you get the localized name, the application won't be localized. The
navigator.language
is the navigator language, so the application has no way of knowing (currently) that the system language has changed. This would require a change to how the web platform interfaces with the OS to get the user's language. This has privacy issues, as it helps narrow down a user's geographic location down to a country. The HTML5 spec currently tries to protect users from this by telling the UA to always report "en-US".