[mpeg-OTspec] RE: Time zone ambiguity

[Adam Twardoch (List)]

I always thought the time zone intended there is California, the current center of the world :) 

(Or, "wherever Sampo was at the time." :) ). 

A.

Sent from my mobile phone.

> On 29.08.2014, at 20:30, "David Lemon lemon at adobe.com [mpeg-OTspec]" <mpeg-OTspec-noreply at yahoogroups.com> wrote:
> 
> It certainly makes sense to me. I would have assumed that this was the intent anyway. (Perhaps a good example of the dangers of assumptions!)
> 
> thanks,
> 
> David L
> 
>  
> 
> From: mpeg-OTspec at yahoogroups.com [mailto:mpeg-OTspec at yahoogroups.com] On Behalf Of 'Levantovsky, Vladimir' vladimir.levantovsky at monotype.com [mpeg-OTspec]
> Sent: Friday, August 29, 2014 8:59 AM
> To: Opstad, Dave; mpeg-OTspec at yahoogroups.com
> Subject: [mpeg-OTspec] RE: Time zone ambiguity
> 
>  
> 
> 
> 
> 
> 
> Hi Dave,
> 
>  
> 
> Thank you for bringing this up. I don’t think adding a clarifying note about UTC/GMT time zone would be an issue, I would let people in this group to consider the possible implications of such change and, if no objections are raised – I will add this clarification as one of the ballot comments.
> 
>  
> 
> Thank you,
> 
> Vladimir
> 
>  
> 
>  
> 
> From: mpeg-OTspec at yahoogroups.com [mailto:mpeg-OTspec at yahoogroups.com] On Behalf Of 'Opstad, Dave' dave.opstad at monotype.com [mpeg-OTspec]
> Sent: Friday, August 29, 2014 11:46 AM
> To: mpeg-OTspec at yahoogroups.com
> Subject: [mpeg-OTspec] Time zone ambiguity
> 
>  
> 
> 
> 
> 
> There is an ambiguity in the original TrueType spec that has, unfortunately, continued right up to this latest OFF spec. Specifically, in the 'head' table, the "modified" and "created" fields are listed as 64-bit counts of seconds since an epoch of "12:00 midnight, January 1, 1904". Unfortunately no time zone is specified, and this has led to ambiguity where a font is modified by some tool in, say, Germany, and is then run through validation code in California, where a complaint is raised that "the modification date is in the future".
> 
>  
> 
> I wonder if it would be possible to include a clarifying note in the spec that GMT/UTC is the time zone of choice for these fields?
> 
>  
> 
> Cheers,
> 
> Dave
> 
>  
> 
> From: <'Levantovsky>, "Vladimir' vladimir.levantovsky at monotype.com [mpeg-OTspec]" <mpeg-OTspec-noreply at yahoogroups.com>
> Reply-To: "Levantovsky, Vladimir" <Vladimir.Levantovsky at monotype.com>
> Date: Monday, August 25, 2014 9:24 AM
> To: "mpeg-OTspec at yahoogroups.com" <mpeg-OTspec at yahoogroups.com>
> Subject: [mpeg-OTspec] AHG Kick-off and the new mandate
> 
>  
> 
>  
> 
> Dear AHG members,
> 
>  
> 
> I am happy to report that the text of the 3rd edition of ISO/IEC 14496-22 “Open Font Format” standard has been promoted to Draft International Standard stage and the ballot is now published. The text has been made public and can be downloaded for review using the following link:
> 
> http://mpeg.chiariglione.org/standards/mpeg-4/open-font-format/text-isoiec-dis-14496-22-3rd-edition
> 
>  
> 
> The AHG mandate is “to study the DIS of the ISO/IEC 14496-22 3rd edition and solicit technologies to further improve it”. I would like to ask you to review the text and provide your suggested changes which can be incorporated as ISO ballot comments. At this stage, we can only suggest comments that incorporate clarifications and improvements to what is already included in the standard, proposals for new technologies can be considered as future new work items and would require an amendment.
> 
>  
> 
> Thank you very much for your contributions!
> 
> Vladimir
> 
>  
> 
> 
> 
> 
>  
> 
> 
> 
> 
> 
> 
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.aau.at/pipermail/mpeg-otspec/attachments/20140830/33593b30/attachment.html>