DR 09-0012 _ Parts, Font Part: Incomplete definition for Font Part

[Chris Rae]

Hi Suzuki-san - proposed final changes attached. I've basically taken your suggestions (and Rex's) but I moved the mention of TTC into an informative note (because it's already been implied by the reference to section 3.6).

What do you think?

Chris

-----Original Message-----
From: mpsuzuki at hiroshima-u.ac.jp [mailto:mpsuzuki at hiroshima-u.ac.jp] 
Sent: 27 October 2010 06:49
To: Chris Rae
Cc: e-SC34-WG4 at ecma-international.org; mpsuzuki at hiroshima-u.ac.jp; eb2m-mrt at asahi-net.or.jp
Subject: Re: DR 09-0012 _ Parts, Font Part: Incomplete definition for Font Part

Dear Chris,

I propose to exclude TTC format from the list of acceptable font formats, if existing implementation of OOXML had never embedded TTC. Embedding TTC has several problems:

- current OOXML spec does not define a method to specify
  a face in multiple faces in TTC. This was filed as DR 09-0047.
  In the discussion to close DR 09-0047, the existing
  implementations were checked ans TTC support was dropped.
  So, the second item should be described as:

  * application/x-font-ttf specifies that the font shall be
    stored in a format conforming to Open Font Structure
    defined in ISO/IEC 14496-22:2008 section 3.5.
    The TrueType Collection format defined in ISO/IEC
    14496-22:2008 section 3.6 must not be used.

- the obfuscation requires a GUID to restore original font.
  if multiple faces in a TTC are used in the document,
  the multiple faces from single TTC font should share
  same GUID? Or, to assign different GUID to multiple faces,
  single TTC font should be obfuscated by multiple GUIDs
  and multiple obfuscated objects from single TTC should
  be embedded? I think both are not good idea. So I propose
  to exclude TTC from the obfuscated font.

    * application/vnd.openxmlformats_officedocument.obfuscatedFont
      specifies that the font is obfuscated using the algorithm
      specified by Font Embedding (section 17.8.1). The source
      font shall be stored in a format conforming to Open Font
      Structure defined in ISO/IEC 14496-22:2008 section 3.5.
      TrueType Collection format defined in ISO/IEC 14496-22:2008
      section 3.6 must not be used.

In addition, before the list of 3 media type, "can be stored in one of *TWO* formats" should be replaced by "can be stored in one of *THREE* formats".

Regards,
mpsuzuki

On Mon, 25 Oct 2010 19:56:25 +0000
Chris Rae <Chris.Rae at microsoft.com> wrote:

>http://cid-c8ba0861dc5e4adc.office.live.com/view.aspx/Public%20Document
>s/2009/DR-09-0012.docx
>
>This is an easy one - we agreed in Tokyo that any OpenType font could be obfuscated. I volunteered to write up the changes, which only involved removing the use of "TrueType/OpenType" in the solution (which is misleading). The new changes are attached. I think we can probabably close this DR quickly on the next call.
>
>Rex - the text modified by this DR lies very close to the accepted text proposed for DR 09-0039. They don't cross over, but there was a note in 09-0039 that it was pending the resolution of this one, so I thought I'd let you know.
>
>Chris
>

-------------- next part --------------
A non-text attachment was scrubbed...
Name: DR 09-0012 proposed changes.docx
Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document
Size: 53662 bytes
Desc: DR 09-0012 proposed changes.docx
URL: <http://mailman.vse.cz/pipermail/sc34wg4/attachments/20101115/f9293962/attachment-0001.bin>