<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif;">
<div>In initial discussions, ‘OSVG’ was to be the sfnt signature for SVG-in-OT fonts that did not require a CFF or glyf table also to be present:</div>
<div><br>
</div>
<div> <a href="http://lists.w3.org/Archives/Public/public-svgopentype/2012Jun/0003.html">http://lists.w3.org/Archives/Public/public-svgopentype/2012Jun/0003.html</a></div>
<div><br>
</div>
<div>Of course SVG could still optionally be present for ‘OTTO’ (CFF) and 1.0/’true’ TT fonts as well. But the ‘OSVG’ thing was scrapped because it was too controversial.</div>
<div><br>
</div>
<div>It would certainly be useful for embedded systems or other situations where the font wouldn’t be exposed to legacy (i.e. non–SVG-in-OT–savvy) engines. Here’s a very concrete example: I use an SVG-in-OT font as a webfont for my website’s banner, but construct
my page so that if the browser is not Firefox, an equivalent graphic is shown instead of SVG-in-OT text. Why should I burden that web font with CFF or TT outlines when they will never be used?</div>
<div><br>
</div>
<div>’OSVG’ can always be proposed (again) at some point in the future, and I have a feeling that that will happen. Note that engines shouldn’t be required to support ‘OSVG’ just as they aren’t required to support the SVG table, or COLR/CPAL, or the ‘name’
table (a PDF renderer for example may never need to read a ‘name’ table), or the entire TT hinting system. I know of CFF-only and TT-only engines as well.</div>
<div><br>
</div>
<div>Sairus</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span>"'Adam Twardoch ' <a href="mailto:list.adam@twardoch.com">
list.adam@twardoch.com</a> [mpeg-OTspec] (List)" <<a href="mailto:mpeg-OTspec-noreply@yahoogroups.com">mpeg-OTspec-noreply@yahoogroups.com</a>><br>
<span style="font-weight:bold">Reply-To: </span>"<a href="mailto:list.adam@twardoch.com">list.adam@twardoch.com</a>" <<a href="mailto:list.adam@twardoch.com">list.adam@twardoch.com</a>><br>
<span style="font-weight:bold">Date: </span>Friday, November 21, 2014 at 12:20 AM<br>
<span style="font-weight:bold">To: </span>"<a href="mailto:mpeg-OTspec@yahoogroups.com">mpeg-OTspec@yahoogroups.com</a>" <<a href="mailto:mpeg-OTspec@yahoogroups.com">mpeg-OTspec@yahoogroups.com</a>><br>
<span style="font-weight:bold">Cc: </span>"<a href="mailto:public-svgopentype@w3.org">public-svgopentype@w3.org</a>" <<a href="mailto:public-svgopentype@w3.org">public-svgopentype@w3.org</a>><br>
<span style="font-weight:bold">Subject: </span>[mpeg-OTspec] OFF with glyphs only in 'SVG ' table?<br>
</div>
<div><br>
</div>
<div>
<div style="background-color: #fff;"><span style="display:none"> </span>
<div id="ygrp-text">
<p>Simple question: does the OFF spec allow an OFF font where the glyph images would only be hosted using the 'SVG ' table, without 'glyf' or 'CFF '?
<br>
<br>
AFAIK, the spec permits to only have 'EBDT'/'EBLC', without any outline data, so my guess 'SVG ' only would also be permitted. Correct?<br>
<br>
If that is the case, what would be the first four bytes? \00\01\00\00? I.e. is my understanding correct that 'OTTO' is only to be used if the 'CFF ' table is present, while any other glyph flavors ('glyf', 'SVG ', 'EBDT'/'EBLC' and possibly others) mandate
\00\01\00\00?<br>
<br>
Best,<br>
Adam<br>
<br>
</p>
</div>
<!-- end group email --></div>
</div>
</span>
</body>
</html>