Some sentences above are wrong. Please, consider rewriting it knowing the info below.

CLDR is primarily distributed in the [LDML format](http://www.unicode.org/reports/tr35/). The release v24 supports 238 languages, and 259 territories - 740 locales in total. The LDML data per language is **not resolved** by the nature, because it supports inheritance. When an implementation doesn't find an item in a language, it knows how it should fallback to find such data in the parent language bundle, or the parent item. The implementation should load more than one language bundle to have the complete data to process.

CLDR is also distributed in the [JSON format](http://cldr.unicode.org/index/cldr-spec/json). Although, differently from the above, only the top 20 languages [1] (not all the CLDR languages) are distributed here. Another big difference is that the data per language in the JSON format is **resolved**. It means that no inheritance needs to take place in here. Loading only the data bundle of interest is enough for completeness.

1: John Emmons is the maintainer of the JSON binding tool, and he once wrote me: "The files in json.zip contain the complete data sets as far as the amount of data per language.  However, for the JSON sample, we only generate the data for the top 20 or so languages, what we consider the "most used" languages in CLDR.  If you want all of the languages in the CLDR, or if you want organize the JSON in a different way than the default configuration, or if you want to skinny down the JSON so that your JSON contains only those fields from the CLDR that you actually need, then you will want to use the tool to do so."