On 4/8/2016 2:26 PM, I wrote: > It would be nice to accept offsets in all formats valid to DEFINE > TIMEZONE or ISO 8601, with or without a blank before the time zone or > offset. East, West, and Z could conflict with valid CP time zones, though.
Wait, no, allowing blanks would get way too messy, since currently DELAY looks only at the first word. But a valid time zone could start with a number, which really throws a wrench in the works. So maybe require = before a time zone name, and then Z is unambiguous: 03:00z 3AM UTC 03:00=z 3AM Z (as defined to CP) 03:00-0400 3AM EDT 03:00w4 3AM EDT 03:00=EDT 3AM EDT (as defined to CP) 03:00*-2.0 3AM two hours west of here 03:00= 3AM in the current time zone, ignoring time change But East and West still conflict badly with zone names: 03:00=we4 4 hours west of current, 4 hours east of W, or zone WE4? ¬R
