<html><head></head><body><div class="ydp15bb34d0yahoo-style-wrap" style="font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:16px;"><div></div>
<div>Dear Toshiya Kun,</div><div><br></div><div>AFAIK, skia milestones and Google chrome versioning are in sync, and the OT-SVG support is in m103, and right next to and after the COLRv1 code too - the skia source code is full of</div><div><br></div><div>If glyphcontext == colrv0 </div><div> do stuffA </div><div>else if glyphcontext = colrv1</div><div> do stuffB</div><div>else if glyhcontext = SVG</div><div> do stuffC</div><div><br></div><div>And I also checked that the COLRv1 code is introduced in m98.</div><div><br></div><div>Yes, I read the chromium issue 306078 issue last night, it is 10 years old. The most recent response from Google folks about "won't fix" is before m103.</div><div><br></div><div>I think Google folks did the work in 2022 but chose to leave it somewhat disabled/crippled. It looks like it should be able to load OT-SVG font with freetype. If you have a lot of OT-SVG fonts on your hard disk and you are on linux, I would consider putting them under ~/.fonts (the personal fontconfig location) and write a custom Web page to try to display them.</div><div><br></div><div>Anyway, with my recent work, any application that uses freetype just needs to copy two new files plus adding one line of code to enable OT-SVG support (plus the rest of skia) so there is no excuse not to...</div><div><br></div><div>It is certainly glaring for a 10-years-old issue full of comments.</div><div><br></div><div>Hin-Tak</div><div><br></div>
<div id="ydp15bb34d0yahoo_quoted_0164990639" class="ydp15bb34d0yahoo_quoted">
<div style="font-family:'Helvetica Neue', Helvetica, Arial, sans-serif;font-size:13px;color:#26282a;">
<div>
On Friday, 14 July 2023 at 02:43:44 BST, suzuki toshiya <mpsuzuki@hiroshima-u.ac.jp> wrote:
</div>
<div><br></div>
<div><br></div>
<div><div dir="ltr">Dear Hin-Tak,<br></div><div dir="ltr"><br></div><div dir="ltr">The Google Chrome m103, the web browser released on the late 2022-06<br></div><div dir="ltr">( <a href="https://chromium.googlesource.com/chromium/src/+log/103.0.5060.53..103.0.5060.66?pretty=fuller&n=10000" rel="nofollow" target="_blank">https://chromium.googlesource.com/chromium/src/+log/103.0.5060.53..103.0.5060.66?pretty=fuller&n=10000</a> ),<br></div><div dir="ltr">supported OT-SVG?<br></div><div dir="ltr"><br></div><div dir="ltr">According to <a href="https://bugs.chromium.org/p/chromium/issues/detail?id=306078" rel="nofollow" target="_blank">https://bugs.chromium.org/p/chromium/issues/detail?id=306078</a> ,<br></div><div dir="ltr">a feature request for OT-SVG support was closed as "wont fix" on 2021.<br></div><div dir="ltr"><br></div><div dir="ltr">My Google Chrome 114 reports "OpenType-SVG is not supported" on<br></div><div dir="ltr"><a href="https://pixelambacht.nl/chromacheck/" rel="nofollow" target="_blank">https://pixelambacht.nl/chromacheck/</a> , it sounds consistent with the<br></div><div dir="ltr">status of this feature request.<br></div><div dir="ltr"><br></div><div dir="ltr">However, although this feature request was closed, some people still post<br></div><div dir="ltr">some comments.<br></div><div dir="ltr"><br></div><div dir="ltr">Regards,<br></div><div dir="ltr">mpsuzuki<br></div><div dir="ltr"><br></div><div dir="ltr">On 2023/07/14 1:59, Hin-Tak Leung wrote:<br></div><div dir="ltr">> I see the future of OT-SVG as falling into half-half. There are technical/implementation details, but also overall strategies and decisions from stakeholders. One glaring(?) aspect is certainly that Google's chrome team supports COLRv1 (not yet a OFF spec) in m98, earlier than OT-SVG (in 4th edition in 2019) in chrome m103...<br></div></div>
</div>
</div></div></body></html>