Re: [icu-design] Jitterbug 4716 - automate integration of new Olson data

[Erik v. d. P. <er...@go...>]

We start with textual rules such as:

[1] northamerica (from ftp://elsie.nci.nih.gov/pub/tzdata2005p.tar.gz)

The stock zic compiler converts these rules to binary files such as:

[2] /usr/share/zoneinfo/America/Los_Angeles

ICU patches zic so that it creates a different textual format:

[3] icu/source/tools/tzcode/zoneinfo.txt

Now we're talking about getting zic to produce an XML format:

[4] new XML format

What do you guys mean by "straight translation"? Straight from [1]?

By the way, can ICU theoretically read from the [2] format? Or does it 
lack some of the info?

Erik

Markus Scherer wrote:
> On 12/8/05, Deborah Goldsmith <gol...@ap...> wrote:
> 
>>OK. I can do the detailed DTD design if someone can tell me the
>>requirements. Or maybe we should just do a straight translation from
>>the current rule format?
> 
> 
> I think a straight translation is best: We (you and Mark) are asking
> the tz list to put this output format into their tools. Therefore, the
> format should be close to what they are used to.
> 
> As long as it's stable and contains all of the necessary information
> (rules, precomputed dates/times/offsets, canonical names & aliases,
> etc.), it will be usable by ICU and others.
> 
> markus
> 
> --
> Opinions expressed here may not reflect my company's positions unless
> otherwise noted.
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
> for problems?  Stop!  Download the new AJAX search engine that makes
> searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> http://ads.osdn.com/?ad_idv37&alloc_id865&op=click
> _______________________________________________
> icu-design mailing list
> icu...@li...
> To Un/Subscribe: https://lists.sourceforge.net/lists/listinfo/icu-design