hi Eike
there are 2 options that I can see :
1. go with your suggestion, where the localegen tool adds an option to populate fields in the form by reading the data from cldr 2. each CLDR release comes with the OOo XML files already generated from CLDR, which users can download. In this case, users would still need to populate the proprietary OOo XML fields by hand which is not so user friendly, but would be easy to do.

I prefer option 1.
Alberto : what do you think of this idea ? would you be able to implement this in your tool ?

Peter

Eike Rathke wrote On 09/26/06 12:35,:
Hi Peter,

On Mon, Sep 11, 2006 at 13:29:33 +0100, Peter Nugent wrote:


the tools should be avaailble for download from :
http://unicode.org/Public/cldr/1.4.0/
where core.zip contains the 1.4 data. the 1.4 tools should also be posted to the same location soon.

but for now you can get the latest CVS snapshot of tools and data at :
ftp://ftp.unicode.org/Public/cldr/cldr-repository-daily.tgz


Well, yes, I know that data is downloadable and tools may be built from
the repository. But this is too cumbersome for localizers who just want
to create some locale data for their locale of interest. They need
a "generate from CLDR" or "enter data here" form similar to the Locale
Generator available at http://www.it46.se/localegen/

The CLDR tools are really fine (I appreciate) for the tedious work of
locale data audits and merging data from CLDR to OOo, but in the current
state are nothing for an end user, which most locale data submitters are
to be considered in this context. Encouraging people to generate OOo
locale data from data already available at CLDR is hard if using the
tools is much harder than creating the data from scratch using other
tools.

As the it46 generator is already able to generate CLDR data as well,
maybe it could be an option to teach it to merge existing CLDR data to
a new OOo locale data?

  Eike


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to