# CLDR and Globalize

**URL:** <https://www.ruby-forum.com/t/cldr-and-globalize/108581>\
**Category:** Rails I18n\
**Created:** [July 5, 2007, 12:41am UTC](https://www.ruby-forum.com/t/cldr-and-globalize/108581 "2007-07-05T00:41:10Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Patrick\_Hall](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/p/f6c823/32.png) [@Patrick\_Hall](https://www.ruby-forum.com/u/Patrick_Hall)\
**Post date:** [July 5, 2007, 12:41am UTC](https://www.ruby-forum.com/t/cldr-and-globalize/108581/1 "2007-07-05T00:41:10Z")

</div>

Hi folks,

I have been digging around in various i18n packages, and so far my  
team is leaning toward Globalize, it seems like an active and usable  
project.

Question:

How is the data in globalize/trunk/data/ populated?

I’m not sure if this has been discussed in this list, but there is a  
huge amount of localization information in the Common Locale Data  
Repository (CLDR):

> **[Unicode CLDR](https://cldr.unicode.org)**
>
> News
> 2023-06-15	CLDR v43.1 released (an update to CLDR v43)
> 2023-04-12	CLDR v43 released
> What is CLDR?
> The Unicode Common Locale Data Repository (CLDR) provides key building blocks for software to support the world's languages, with the largest and...

(Not only is the data extensive, it’s also localized into several  
languages – you can get at how to say “Japanese” in Spanish, “Russia”  
in Swahili, etc.)

It seems like tracking the data in CLDR would be much easier to  
maintain than trying to maintain the data just for the Globalize  
project.

Best regards,

Pat Hall