Aa is a general substitute for Å, no matter which form the official name of the town is. But the sort order is still that of Å, so Aa is treated the same as Å - only for Danish towns, of course, where this substitution is done.
So if you have a list of Aachen, Aabenraa, Zürich the correct Danish sort order is Aachen, Zürich, Aabenraa.
On why Århus — sorry Aarhus — changed its spelling: “The background for changing the spelling is to make the city more visible on the Internet, where å always is spelled aa.”
If browsers did not implement .ToLocaleString before, is there much hope that they will implement even better specs? I hope so.
IMHO any OS should provide the user with their choice of formatting and collation preferences, etc. This is generally true already. Next, all apps including browsers need to honor those preferences. This approach provides both consistency across devices (user picks what they like once per device or can even have their preferences replicate across their devices) AND it allows customization that is unconstrained by the outdated 'locale model' (in which people magically share the same set of preferences as their countrymen.
By being able to call JavaScript without a 'locale' and thus 'use the underlying user preferences' simple generic code can work for everyone.
The only actually useful use of pre-named 'locales' is by the OS platform vendors themselves, allowing users to pre-populate their preferences with good defaults.
Funny fact: Århus changed its name to Aarhus two years ago
ReplyDeleteUsed for pedagogical purposes. :)
DeleteThat is not only a funny fact but very relevant.
DeleteAa is a general substitute for Å, no matter which form the official name of the town is. But the sort order is still that of Å, so Aa is treated the same as Å - only for Danish towns, of course, where this substitution is done.
So if you have a list of Aachen, Aabenraa, Zürich the correct Danish sort order is Aachen, Zürich, Aabenraa.
On why Århus — sorry Aarhus — changed its spelling: “The background for changing the spelling is to make the city more visible on the Internet, where å always is spelled aa.”
DeleteSource: http://politiken.dk/indland/ECE1094748/aarhus-skifter-navn/
If browsers did not implement .ToLocaleString before, is there much hope that they will implement even better specs? I hope so.
ReplyDeleteIMHO any OS should provide the user with their choice of formatting and collation preferences, etc. This is generally true already. Next, all apps including browsers need to honor those preferences. This approach provides both consistency across devices (user picks what they like once per device or can even have their preferences replicate across their devices) AND it allows customization that is unconstrained by the outdated 'locale model' (in which people magically share the same set of preferences as their countrymen.
By being able to call JavaScript without a 'locale' and thus 'use the underlying user preferences' simple generic code can work for everyone.
The only actually useful use of pre-named 'locales' is by the OS platform vendors themselves, allowing users to pre-populate their preferences with good defaults.
Are you sure it is implemented into Chrome ?
ReplyDeleteIn the spec : "The Intl object is a standard built-in object that is the initial value of the Intl property of the global object."
And there is no "Intl" object in the global scope in Chrome (23.0.1271.97).