Globalize and CLDR

                                     :                       :
+-----------+       +------------+   :   +-------------+     :   +------------+
| Globalize |------>| CLDR (API) |------>| CLDR (JSON) |-------->| CLDR (xml) |
+-----------+       +------------+   :   +-------------+     :   +------------+
                                     :                       :
                                     : (serverside,          :
(clientside or serverside)           :  possibly clientside) : (serverside)

Globalize

• Should parse or format strings, dates and numbers.

CLDR (API)

• Should figure out the tuple (language, region, script) given a locale (eg. en, pt_BR, jp). Algorithm at unicode.org/tr35#Likely_Subtags (Add Likely Subtags).

CLDR (JSON)

• Should load JSON-CLDR data.
• Should get the inheritance-resolved value for each key.
• Should resolve inheritance unicode.org/tr35#Locale_Inheritance.

CLDR (xml)

• Should load xml-CLDR data.
• Should return JSON corresponding tree.

Research

• Investigate how chromium/blink i18n works. This seems interesting https://github.com/dstockwell/blink/blob/d294b41abc2e2f9e7ce5704b34a2da01259d5054/LayoutTests/fast/js/script-tests/i18n-bindings-locale.js
• Twitter has a CLDR lib. https://github.com/twitter/twitter-cldr-js . But, it seems weird.