RE: bug with date_convert_universal()

does EMI protocol has any hints as to what the SMSC things the local
time zone is ? if so, then you can translate back to GMT before calling
convert_date_universal(), as AT2 does.

--
Oded Arbel
m-Wise Inc.
[email protected]

The palest ink is better than the best memory.
	-- Chinese Proverb


> -----Original Message-----
> From: Angel Fradejas [mailto:[email protected]]
> Sent: Wednesday, March 13, 2002 11:44 AM
> To: Andreas Fink; Richard Braakman
> Cc: [email protected]
> Subject: RE: bug with date_convert_universal()
> 
> 
> >>Okay, someone sent me the CMG EMI 3.5 spec.  The only specification
> >>of the date format it has is "DDMMYYhhmmss" without further 
> explanation.
> >>Since we have evidence of at least one EMI SMSC using 
> 1-based months,
> >>shall we assume that they all do?  It would make sense, if 
> the lack of
> >>specification means that the date format is intended to be 
> human-readable.
> 
> 
> >this is definitively the case. The EMI timestamps are also is in
> >LOCAL TIME, not GMT
> 
> Yes, that's right. My SMSC works with 1-based months and 
> local time. So it
> seems we cannot use date_convert_universal as it is for EMI2 
> timestamps.
> 
> Besides the 1-based/0-based month problem, it assumes GMT timestamps.
> 
> Angel Fradejas.
> 
> 
>