Description
It might be more user and developer friendly in our polyfill to support parsing of the <mapml-viewer lang="en|fr|sv|uk|etc">
lang
attribute (to the extent that we have internationalized message strings for the language). Currently, the map relies on the <map-options>
tag to obtain the language of the "browser", but perhaps allowing control of the localization of the map interface by the lang
attribute would be user and developer friendly, being as it would be under the control of the author. Currently, the language of the map can be forced by some tricks, for example on this experiment. (Source).
For example, while the injected <map-options>
could and should specify what language is selected by the user's "browser" (simulated or provided by our mapml-extension chromium extension, currently), maybe it would be cool to be able to override that default language and provide the map localization in the author-selected lang
value. That's what is happening in this MDN example, (although the only user interface requiriing localization is the text entered by the author).
One consequence of implementing this would be to force us into shipping UI localized strings with the bundle. Other ideas below!