On Fri, May 3, 2013 at 10:36 AM, John Haxby <john.haxby@oracle.com> wrote:
On 02/05/13 22:15, Alan Perry wrote:
On 5/2/13 1:58 PM, random832@fastmail.us wrote:
On Thu, May 2, 2013, at 15:46, Tobias Conradi wrote:
"The daylight saving time rules to be used for a particular time zone are encoded in the time zone file" Should read: ...encoded in the time zone rule file.
Except that they are called 'time zone data files' in the tzcode README ...
Since evidently certain people are unable to understand anything other than perfect pedantic precision in describing things.
The documentation of the tz database sometimes uses inconsistent terminology and doesn't spell everything out like a formal standard or most industry specs would. Does it need that now?
I don't believe so. Any reasoning?
We've had one person who thought tabs were important whereas common practice (and the code) treats sequences of tabs and spaces as white space separators. That sounds more as a reason to have better documentation.
I don't think we actually need to change anything at all with regard to this: the tzdata and tzcode function perfectly well. Having better documentation to allow people understanding the IANA time zone database better, wouldn't deteriorate that, would it?
-- Tobias Conradi Rheinsberger Str. 18 10115 Berlin Germany http://tobiasconradi.com