cldr

This is why the <q> element exists which enables locale-aware quotation marks: https://w3c.github.io/i18n-drafts/questions/qa-the-q-element... :root:lang(en) { quotes: '“' '”' '‘' '’' } :root:lang(fr) { quotes: '«' '»' '«' '»' } :root:lang(fr-CA) { quotes: '«' '»' '‹' '›' } q:before { content: open-quote; } q:after { content: close-quote; } There's currently 26 quotation mark varieties by default (in Firefox): https://searchfox.org/firefox-main/source/intl/locale/cldr-q... which are sourced from the Unicode Common Locale Data Repository: https://github.com/unicode-org/cldr/tree/main/common/main

And ICU uses data from CLDR, which is mentioned in the blog. Here, there are 380 xml files: https://github.com/unicode-org/cldr/tree/main/common/transfo... Yes, ICU is ubiquitous. But, some NLP projects use various other libraries, such as uroman (just for romanization - to Latin script).

No, unicode define the region subtags here https://github.com/unicode-org/cldr/blob/maint/maint-41/comm... You can see the country names alongside the codepoints here, ctrl+f for 'taiwan' and 'palestinian territories' https://unicode.org/Public/emoji/latest/emoji-sequences.txt

One problem I stumbled upon frequently is codebases that did not support localized formats, but just assumed a certain format to use, for example through concatenation. There are capabilities built into the programming languages, which allow to format numbers, currencies, etc. with a specific locale. There are also great resources [1] out there that provide all kinds of formats and localized names for countries, currencies, etc. [1] Unicode CLDR: https://github.com/unicode-org/cldr