> Apple's current error checking makes it very difficult to set dates that are
> past 2040. The vast majority of the functions exposed in the API will
> "cleverly" assume that you really meant a year in the range 1941-2040 and
> may munge your correctly input 1937 to 2037 behind your back.
>
Looking at the API documentation, I do not see where this occurs for fully
specified dates, e.g., "2041" instead of "41." Just where is this occurring?
Are you assuming the long date time structures are not used?
> Apple has committed to resolving these issues "in a timely fashion";
> however, they've not defined "timely".
>
It seems to me that this has already been resolved...
>
> For all I know, Entourage may do this all wrong (although I suspect that
> they didn't go through the trouble of writing their own date and time
> utilities). But it's not the case that if Entourage fails to display a 2041
> date that ipso facto they're not using the OS routines.
It appears to me that Entourage does not use the long structures, and that
is the reason that the message wraps to a date of 1905. However, this does
cause the potential data loss I referred to previously. It also implies that
certain language variants and calendar settings would have problems - such
as a Hebrew with Jewish calendar, and any Buddhist calendar.
--
Eric Hildum
--
To unsubscribe: <mailto:[EMAIL PROTECTED]>
To search the archives:
<http://www.mail-archive.com/entourage-talk%40lists.boingo.com/>
