<html 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=utf-8">
<meta name="Generator" content="Microsoft Word 15 (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:Aptos;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:12.0pt;
font-family:"Aptos",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#467886;
text-decoration:underline;}
span.EmailStyle20
{mso-style-type:personal-compose;
font-family:"Aptos",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:11.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body lang="EN-US" link="#467886" vlink="#96607D" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt">></span> Guess OT-SVG support was broken when MS Edge moved to a Chromium-based backend in April 2021.<br>
<br>
<span style="font-size:11.0pt"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">That’s correct.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Peter<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> Hin-Tak Leung <htl10@users.sourceforge.net>
<br>
<b>Sent:</b> Monday, February 12, 2024 3:07 PM<br>
<b>To:</b> mpeg-otspec@lists.aau.at; Jonathan Kew <jfkthame@gmail.com>; Peter Constable <pconstable@microsoft.com><br>
<b>Cc:</b> suzuki toshiya <mpsuzuki@hiroshima-u.ac.jp><br>
<b>Subject:</b> [EXTERNAL] questions on OT-SVG in Chrome, MS Edge and Firefox<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">Hi,<br>
<br>
I have continued to keep the blink/skia patches [1] up to date to current Chromium. And continue to test them [2] with QT WebEngine, which is a slimmed-down Chromium code variant up to about 3 months behind in latest Chromium development. Am trying to get the
QT folks to take the patches [3].<br>
<br>
Since some claimed that MS Edge supports OT-SVG back in 2017, and MS Edge has been available for Linux for a while, I gave it a try, and it is a NO. Guess OT-SVG support was broken when MS Edge moved to a Chromium-based backend in April 2021.<br>
<br>
Anyway, here is a question for Peter and possibly also other Microsoft folks:<br>
<br>
- I have no idea how much current MS Edge on windows differs from Chrome on windows, but would you pass the URL for the patches to the relevant people and let them see what they see fit to adapt please? Thanks. Feedbacks and corrections/modifications can go
to [1]'s issues, etc or directly/privately to me if needed.<br>
<br>
And here is a question for Jonathan, and possibly other Firefox folks:<br>
<br>
- logically my chrome patches are in 3 parts, a one-liner switching OT-SVG support on in Skia, tell OTS to let such fonts pass-through as a usable font format, and get Blink to use freetype for non-OS-native font formats similar to sbix for windows etc. The
2nd part is somewhat common to Firefox - how does firefox deal with OT-SVG web-font sanitizing-wise? Does its copy of OTS (AFAIK) let them through and just hope the SVG processing is robust enough, or do some XML/etc validation on the way?<br>
<br>
Would like to hear what Safari/Apple folks or webkitgtk folks (both of them supoprts OT-SVG, the latter I tested myself with webkitgtk-sharp) who like to comment on the sanitizing/security aspect of OT-SVG web fonts too.
<br>
<br>
Hin-Tak<br>
<br>
<br>
[1] <a href="https://github.com/HinTak/chromium-mod-CI">https://github.com/HinTak/chromium-mod-CI</a><br>
[2] <a href="https://github.com/HinTak/Qt6WE-OT-SVG">https://github.com/HinTak/Qt6WE-OT-SVG</a><br>
[3] <a href="https://bugreports.qt.io/browse/QTBUG-120543">https://bugreports.qt.io/browse/QTBUG-120543</a>
<o:p></o:p></p>
</div>
</div>
</body>
</html>