Home | History | Annotate | only in /external/cldr/tools/java
Up to higher level directory
NameDateSize
.classpath22-Oct-2020991
.project22-Oct-2020369
.settings/22-Oct-2020
build.xml22-Oct-202012.2K
cldr-tools.properties22-Oct-2020823
com/22-Oct-2020
find-unrun-tests.sh22-Oct-2020712
how_to_notes.txt22-Oct-202092
libs/22-Oct-2020
org/22-Oct-2020
readme.txt22-Oct-20201.9K

readme.txt

      1 CLDR Tools ReadMe
      2 -----------------
      3 
      4 The tools folder will contain tools, tests, and utilities for dealing with CLDR data.
      5 The code is very preliminary, so don't expect stability from the APIs (or documentation!),
      6 since we still have to work out how we want to do the architecture.
      7 
      8 See: http://cldr.unicode.org/development/new-cldr-developers
      9 
     10 The directory structure is:
     11 [./org/unicode/cldr..]
     12 icu  	Tools for generating ICU-format data from CLDR
     13 posix	Tools for generating POSIX-format data from CLDR
     14 test	Test tools for CLDR
     15 json    Tools for creating JSON data from CLDR
     16 tool	Tools for manipulating CLDR files
     17 util	Utilities for handling CLDR files
     18 ooo 	OpenOffice.org tools for :
     19 			- Converting OpenOffice.org format to LDML
     20 			- CLDR data to OpenOffice.org format
     21 			- Comparing OpenOffice.org data
     22 -----------------
     23 
     24 The tools may use ICU4J code for testing, but should use none of the data in ICU4J.
     25 We'll be using the ICU4J test framework also (we looked at JUnit, but it would be
     26 really clumsy for the ways in which we'd have to test).
     27 
     28 
     29 TO BUILD AND RUN THE TOOLS:
     30 
     31   See http://cldr.unicode.org/tools
     32 
     33 ADVANCED USAGE:
     34 
     35 1.  Build the tools with the following command:
     36 
     37    ant clean all jar
     38 
     39 2. For a list of build targets use the following command:
     40 
     41    ant -projecthelp
     42 
     43 3. For running automated and console tests, you will want to create a 'build.properties' file.
     44 
     45     If you checked out CLDR as one directory (i.e. there is a ../../common relative to this readme),
     46     then create build.properties containing:
     47 
     48               CLDR_DIR=../..
     49 
     50     Otherwise, if inside of an eclipse workspace (i.e. there is a ../common relative to this readme),
     51     this may work for you:
     52 
     53               CLDR_DIR=..
     54 
     55 CLDR TOOL DEVELOPMENT ON ECLIPSE IDE
     56 
     57    Eclipse project files are available for CLDR Tools development.
     58    To set up the environment on Eclipse IDE, see the link:
     59 
     60    http://cldr.unicode.org/development/new-cldr-developers
     61