[Unicode]   Common Locale Data Repository : Bug Tracking Home | Site Map | Search

CLDR Ticket #9695(accepted docs)

Opened 2 years ago

Last modified 5 months ago

Describe how to use the tools for POSIX and JSON

Reported by: mark Owned by: emmons
Component: json Data Locale:
Phase: spec-beta Review:
Weeks: Data Xpath:


From Karl:

I can't find these that are mentioned in http://cldr.unicode.org/

"For those interested in the source CLDR data, it is available for each release in the XML format specified by LDML. There are also tools that will convert to JSON and POSIX format. For more information, see CLDR Releases/Downloads."

If you follow that link, the page contains this text:


"Note: Beginning with CLDR v21, the CLDR project will no longer publish POSIX-format locale sources as part of its distribution. The POSIX locale generation tools will continue to be made available as a part of the release. Developers who require POSIX compliant locales can generate them using these tools."

But I can't find those tools.


​That is a bit obscure! We stopped generating the source for POSIX because essentially every user customized it in some way, so was better to do with a tool. We need to add a pointer to where to get the tools and how to use them.

  • For where they are, see http://cldr.unicode.org/index/downloads#Repository_Organization
  • Above that are the details for SVN access.​
  • But we really need a page that describes the specific tools for JSON and POSIX generation, and how to use them. Also how to build fully-resolved CLDR, and how to filter results for all of these.


Change History

comment:1 Changed 2 years ago by mark

  • Owner changed from anybody to emmons
  • Status changed from new to accepted
  • Type changed from unknown to docs
  • Milestone changed from UNSCH to 31

comment:2 Changed 2 years ago by mfl-commissioner@…

now that CLDR 30 has been released, can we get that "how to" page now, pretty please? Release 27.0 had a cldr.jar but that hasn't been provided since then.

John M.

comment:3 Changed 21 months ago by emmons

  • Phase changed from dsub to spec-beta
  • Priority changed from assess to minor
  • Component changed from unknown to json

comment:4 Changed 19 months ago by emmons

  • Milestone changed from 31 to 32

comment:5 Changed 12 months ago by emmons

  • Milestone changed from 32 to upcoming

comment:6 Changed 5 months ago by emmons

  • Milestone changed from upcoming to UNSCH

Add a comment

Modify Ticket

as accepted

E-mail address and user name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.