<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal">Dear all,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I am writing to you on behalf of the W3C WebFonts WG that is now developing a new webfont compression technology and webfont data delivery format known as WOFF 2.0.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The new compression technology is partially based on what was previously known as MicroType Express compression, which was implemented on the web as Embedded OpenType (EOT format, see [1]) and has also been used as the foundation of the
MPEG font compression technology defined by ISO/IEC 14496-18 “Font compression and streaming”. The essence of the MTX compression is to remove the built-in redundancy of the generic font format data and restructure the data to make it suitable for high efficiency
entropy coding. As a result, when the font data is compressed and decompressed it is subjected to “lossless modifications”, where the input and output font files retain the exact same functionality and features but are no longer bitwise compatible binary files.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The WOFF 2.0 compression technology is being developed with the same underlying principles in mind – it actually reuses portions of the MTX preprocessing and optimization steps but restructures the data to assemble it in seven different
sub-streams to make the entropy coding more efficient. There is also a new entropy coding mechanisms that was developed to improve compression efficiency.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The OFF ‘head’ table contains ‘flags field I believe that specify various font properties. Bit 11 of that field, as it is currently defined, indicates that<o:p></o:p></p>
<p class="MsoNormal">“<span style="font-size:9.0pt;font-family:"Verdana","sans-serif"">Font data is 'lossless,' as a result of having been compressed and decompressed with the Agfa MicroType Express engine.</span>” I believe that the original intent was to
make an emphasis that a font has been subjected to the lossless transform where the original font functionality is preserved but binary compatibility is lost – MTX (referenced as part of the bit 11 description) was the only known technology at that time to
apply this kind of transformation but the use of this bit should not be limited to MTX only.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">WebFonts WG believes that WOFF2 compliant encoders should also set this flag to indicate the fact that a font file was subjected to the lossless transform (which is similar but not identical to the original MTX) and suggests to modify the
bit 11 description as follows:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">“Bit 11: Font data is ‘lossless’ as a results of having been subjected to optimizing transformation and/or compression (such as e.g. compression mechanisms defined by ISO/IEC 14496-18, MicroType Express, WOFF 2.0 or similar) where the original
font functionality and features are retained but the binary compatibility between input and output font files is not guaranteed. As a result of the applied transform, the ‘DSIG’ Table may also be invalidated.”<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I believe this new definition preserves the original intent of this flag and extends use cases when this flag setting may be a benefit. It will also provide an indication that certain transforms may cause Digital Signature table data be
invalidated as a result.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Comments?<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thank you,<o:p></o:p></p>
<p class="MsoNormal">Vladimir<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>