Re: "Universal Time"

Comments:
>  So with a range of 136 years, it extends back to Dec 1901 and up to  
> Jan 1938.

I assume this is supposed to be 2038.

> MAC_TIME
> ?
> seconds
> Jan 1, 2001

The data type here is double (actually, a typedef CFAbsoluteTime which  
resolves to double).

<http://developer.apple.com/documentation/CoreFoundation/Reference/ 
CFTimeUtils/Reference/DataTypeGroupIndex.html#//apple_ref/c/tdef/ 
CFAbsoluteTime>

Deborah Goldsmith
Internationalization, Unicode liaison
Apple Computer, Inc.
[email protected]

On May 11, 2004, at 2:02 PM, Mark Davis wrote:

> I put a proposal for handling different binary formats of datetime on
> http://oss.software.ibm.com/cvs/icu/~checkout~/icuhtml/design/ 
> formatting/universal_time_scale.html
>
> Feedback is welcome.
>
> Mark
> __________________________________
> http://www.macchiato.com
> ► शिष्यादिच्छेत्पराजयम् ◄
>
> ----- Original Message -----
> From: "George Rhoten" <[email protected]>
> To: "Mark Davis" <[email protected]>
> Cc: <[email protected]>
> Sent: Tue, 2004 May 11 10:44
> Subject: Re: [icu-bug] incoming/3746
>
>
>> Here is the 2 line fix for this issue.
>>
>>         uset_applyPattern(fillIn, exemplarChars, len,
>>                           USET_IGNORE_SPACE | USET_CASE_INSENSITIVE,
>> status);
>>
>> This API is draft 2.8.  It is not internal.
>>
>> George Rhoten
>> IBM Globalization Center of Competency/ICU  San José, CA, USA
>> ICU main website: http://oss.software.ibm.com/icu/index.html
>>
>>
>>
>>
>> "Mark Davis" <[email protected]>
>> Sent by: [email protected]
>> 05/11/2004 10:21 AM
>>
>>         To:     <[email protected]>
>>         cc:
>>         Subject:        Re: [icu-bug] incoming/3746
>>
>>
>> Hmmm. We do have internal API that computes the case-closure of a  
>> set, and
>> that
>> computes the canonical-equivalence closure. Perhaps we should think  
>> about
>> making
>> those public APIs in the future.
>>
>> Mark
>> __________________________________
>> http://www.macchiato.com
>> ► शिष्यादिच्छेत्पराजयम् ◄
>>
>> ----- Original Message -----
>> From: <[email protected]>
>> To: <[email protected]>;  
>> <[email protected]>
>> Sent: Tue, 2004 May 11 08:53
>> Subject: [icu-bug] incoming/3746
>>
>>
>>> new message incoming/3746
>>> URL: http://www.jtcsv.com/cgi-bin/icu-bugs?findid=3746
>>>
>>> ====> ORIGINAL MESSAGE FOLLOWS <====
>>>
>>> From: [email protected]
>>> Date: Tue May 11 11:53:18 2004
>>> Subject: Should exemplar character set be case-insensitive?
>>>
>>> Full_Name: Deborah Goldsmith
>>> Version: 2.8
>>> OS: all
>>> PROJECT: ICU4C
>>> JAVA:
>>> Submission from: (NULL) (24.6.137.96)
>>>
>>>
>>> Right now the API that returns the exemplar character set in  
>>> ulocdata.h
>> just
>>> creates a set directly from the (lowercase-only) locale data.  
>>> Shouldn't
>> it be
>>> specifying the case-insensitive option when creating the set from the
>> pattern
>> in
>>> the locale data? One problem is that once the set is returned, the  
>>> only
>> way to
>>> get the case-insensitive version is to turn it back into a pattern,  
>>> then
>>> recreate the set with the case-insensitive option. There is no public
>> API to
>>> compute the case-closure of an existing set (that would also be an
>> acceptable
>>> solution).
>>>
>>> _______________________________________________
>>> icu-bugrfe mailing list
>>> [email protected]
>>>
>> http://oss.software.ibm.com/developerworks/oss/mailman/listinfo/icu- 
>> bugrfe
>>>
>>
>> _______________________________________________
>> icu mailing list
>> [email protected]
>> http://oss.software.ibm.com/developerworks/oss/mailman/listinfo/icu
>>
>> _______________________________________________
>> icu mailing list
>> [email protected]
>> http://oss.software.ibm.com/developerworks/oss/mailman/listinfo/icu
>>
>
> _______________________________________________
> icu mailing list
> [email protected]
> http://oss.software.ibm.com/developerworks/oss/mailman/listinfo/icu