<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</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>> Where is the actual glyph description that would go into the PDF in a standard OTF/TFF? </div>
<div><br>
</div>
<div>Any number of options spring to mind (each of which will have pros and cons). Here’s some inspiration for further fleshing out:</div>
<div>- choose the fallback CSS font-family in the list or the UA’s default font</div>
<div>- make it so that PDF’s substitution font facility kicks in</div>
<div>- embed as Type 3 (preserves color and scalability of the OSVG)</div>
<div>- rasterize the SVG glyphs in color and embed the bitmaps as Type 3</div>
<div>- rasterize the SVG glyphs in monochrome and embed the bitmaps in PDF</div>
<div>- of course, an OSVG will not be prohibited from having a CFF or glyf table in addition to the SVG; if these are present use them</div>
<div>- embed as SVG OT (if/when PDF decides to support it). I list this here for completeness!</div>
<div><br>
</div>
<div>All of the above, of course, would be subject to the fonts’ licensing considerations.</div>
<div><br>
</div>
<div>> It’s one of the reasons that OSVG was killed in the first place and should NEVER be allowed in the real world.</div>
<div><br>
</div>
<div>
<div>Your point that a webpage using webfonts isn’t a completely closed system is a good one.</div>
<div><br>
</div>
<div>However, I don’t see webpage->PDF conversions working well for the limited set of pages and situations I try it on; these webpages use existing standards. The webpages shouldn’t be prohibited from using those facilities (nor the standards from standardizing
those facilities) just because a particular workflow doesn’t (yet) support them: that should be a decision made by the owner of the website, similar to “should I use xxx on my webpages because it’s not supported in older versions of yyy browser?” and it should
be supported by a clear versioning/fallback scheme.</div>
</div>
<div><br>
</div>
<div>In any case, completely (or adequately) closed systems are an excellent reason for OSVG, but it’s not a proposal that’s on the table for right now.</div>
<div><br>
</div>
<div>Best,</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>Leonard Rosenthol <<a href="mailto:lrosenth@adobe.com">lrosenth@adobe.com</a>><br>
<span style="font-weight:bold">Date: </span>Sunday, November 23, 2014 at 5:33 PM<br>
<span style="font-weight:bold">To: </span>Sairus Patel <<a href="mailto:sppatel@adobe.com">sppatel@adobe.com</a>>, "<a href="mailto:list.adam@twardoch.com">list.adam@twardoch.com</a>" <<a href="mailto:list.adam@twardoch.com">list.adam@twardoch.com</a>>, "<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>Re: [mpeg-OTspec] OFF with glyphs only in 'SVG ' table?<br>
</div>
<div><br>
</div>
<div>
<div 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>
<div>But a mapping is useless without an actual glyph?!?! Where is the actual glyph description that would go into the PDF in a standard OTF/TFF? </div>
<div><br>
</div>
<div>Leonard</div>
<div>
<div id="MAC_OUTLOOK_SIGNATURE"></div>
</div>
</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:12pt; 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>Sairus Patel <<a href="mailto:sppatel@adobe.com">sppatel@adobe.com</a>><br>
<span style="font-weight:bold">Date: </span>Sunday, November 23, 2014 at 7:54 PM<br>
<span style="font-weight:bold">To: </span>Leonard Rosenthol <<a href="mailto:lrosenth@adobe.com">lrosenth@adobe.com</a>>, "<a href="mailto:list.adam@twardoch.com">list.adam@twardoch.com</a>" <<a href="mailto:list.adam@twardoch.com">list.adam@twardoch.com</a>>,
"<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>Re: [mpeg-OTspec] OFF with glyphs only in 'SVG ' table?<br>
</div>
<div><br>
</div>
<div>
<div 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>> Because it means that the browser (or some other consumer of that content) can’t convert the content into some other format (say, PDF) without losing all the important parts of the content being text – searching, indexing, etc.</div>
<div><br>
</div>
<div>Actually, all semantics (searching, indexing, etc) will be able to be perfectly preserved in a webpage->PDF conversion, since the OSVG will contain a cmap. In OFF/OT, the cmap and not the glyph descriptions contain the semantics (Unicode-to-glyph ID mapping). </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>Leonard Rosenthol <<a href="mailto:lrosenth@adobe.com">lrosenth@adobe.com</a>><br>
<span style="font-weight:bold">Date: </span>Saturday, November 22, 2014 at 12:00 PM<br>
<span style="font-weight:bold">To: </span>Sairus Patel <<a href="mailto:sppatel@adobe.com">sppatel@adobe.com</a>>, "<a href="mailto:list.adam@twardoch.com">list.adam@twardoch.com</a>" <<a href="mailto:list.adam@twardoch.com">list.adam@twardoch.com</a>>, "<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>Re: [mpeg-OTspec] OFF with glyphs only in 'SVG ' table?<br>
</div>
<div><br>
</div>
<div>
<div 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>
<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. </div>
<div>></div>
<div>On a completely closed system, that’s perfectly reasonable and I can see that.</div>
<div><br>
</div>
<div>However…</div>
<div><br>
</div>
<div>>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>></div>
<div>Because it means that the browser (or some other consumer of that content) can’t convert the content into some other format (say, PDF) without losing all the important parts of the content being text – searching, indexing, etc.</div>
<div><br>
</div>
<div>It’s one of the reasons that OSVG was killed in the first place and should NEVER be allowed in the real world. It would be great if the SVG-in-OT would clearly spell out the evils of this concept and specifically make any such implementations as invalid.</div>
<div><br>
</div>
<div>Leonard</div>
<div>
<div id=""></div>
</div>
</div>
</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:12pt; 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>Sairus Patel <<a href="mailto:sppatel@adobe.com">sppatel@adobe.com</a>><br>
<span style="font-weight:bold">Date: </span>Saturday, November 22, 2014 at 12:01 AM<br>
<span style="font-weight:bold">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>>, "<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>Re: [mpeg-OTspec] OFF with glyphs only in 'SVG ' table?<br>
<span style="font-weight:bold">Resent-From: </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">Resent-Date: </span>Saturday, November 22, 2014 at 12:02 AM<br>
</div>
<div><br>
</div>
<div>
<div 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></div>
</div>
</span></div>
</div>
</span></div>
</div>
</span></div>
</div>
</span>
</body>
</html>