Where “internationalization” and “localization” meet “web applications” a big subject is “currency”, in terms of how amounts of money are displayed in a country or region of interest. In terms of this today we “channel” the Javascript functionality …
numObj.toLocaleString([locales [, options]]); // where locales=BCP 47 language tag and options is either (like) { style: 'decimal', maximumFractionDigits : 2, minimumFractionDigits : 2 } or (like) { style: 'currency', currency: 'AUD' }
… to combine …
- Language Culture Codes (BCP 47 language tags (is locales above)) to determine an International Keyboard character set to use
- Currency Codes (ISO 4217 currency codes (is part of options above))
… into HTML select “dropdown” elements, around the inspiration of this very useful link, thanks, to piece together the user definable parameters to localize the currency representation of numbers in the user defined “local environment”.
You can see this in play with today’s HTML and Javascript localized_currency.html‘s live run link, that you can try yourself.
If this was interesting you may be interested in this too.



What I find most interesting here is how honestly the post names the hard part: getting focus to work with [element].click() and [element].blur() is the kind of detail that looks trivial until you actually try to drive a page this way. The single-row table that deliberately overflows to the right also makes sense as a design choice, since a radio playlist needs to be scrolled through rather than squeezed into one screen. And the payoff β clicking one song link and having the songs play in sequence and loop back through the list β is a neat reward for all that plumbing with the audio-only YouTube player.