Clint writes: > What should our portable timezone information look like at the > language level? Should one of the existing keywords include > timezone information?
&dateline has been suggested; it's certainly not a big deal to add a timezone string to it (or to ctime() - it currently does a ctime(3) but I think it should do a strftime(3) just like date(1) does. However: > Are there a standard set of strings worldwide for this? There lies the rub! The three letter names used by date(1) are not unique. The ISO standard - ISO 8601 (assuming it hasn't been superseded by a new standard) only talks about timezones as offsets from UTC. Looks like the only standard is zoneinfo - as galling as it is to be associated with LA, I'm in the "America/Los_Angeles" timezone. Then there's daylight savings. The only hope is to use the tz (aka zoneinfo) database - http://www.twinsun.com/tz/tz-link.htm for systems that don't already have it installed. Comments? -s _______________________________________________ Unicon-group mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/unicon-group
