- From: Sairus Patel <sppatel@adobe.com>
- Date: Mon, 15 Aug 2016 17:48:52 +0000
- To: Chris Lilley <chris@w3.org>, "public-svgopentype@w3.org" <public-svgopentype@w3.org>
Hi Chris, Thanks for your color fonts round-up. It’s great that Edge now supports OT-SVG. Support in two major browsers is a good incentive for the others to follow suit. It’s not clear from your message whether you are saying the scaling bug is in Edge/DirectWrite or in the LapisLegit test itself [others: follow link below to see links in Chris’ original post]. I’d heard LapisLegit had a bug whereby oversized glyphs were shown in Win 10. I’ve asked Roel to comment on this. Best, Sairus -----Original Message----- From: W3C Community Development Team <team-community-process@w3.org> Reply-To: Chris Lilley <chris@w3.org> Date: Monday, August 15, 2016 at 7:10 AM To: "public-svgopentype@w3.org" <public-svgopentype@w3.org> Subject: Chromatic fonts - implementation roundup [via SVG glyphs for OpenType Community Group] Resent-From: "public-svgopentype@w3.org" <public-svgopentype@w3.org> Resent-Date: Monday, August 15, 2016 at 7:10 AM >The implementation of SVG glyphs for OpenType in Firefox is well known. Recently >however with the Windows 10 Anniversary Update, I noticed that Microsoft Edge 14 >also now supports them! > >Check to see what your browser supports! > >Unfortunately, there is currently a scaling bug which makes each SVG glyph twice >as big as it should be. But I am sure that will be fixed pretty soon. Compare >these SVG glyphs vs. inline SVG, in Firefox and then in Edge 14. > >A little digging reveals even better news - this isn't an Edge-specific update. >Instead DirectWrite and Direct2D have been updated to support SVG in OpenType >(also the Google CBDT colored PNG glyphs and the undocumented but >reverse-engineered Apple sbix colored raster format. (This is in addition to the >existing COLR/CPAL support that has been there since Windows 8.1). > >Amusingly, this means that Edge 14 has better support for the Google-originated >CBDT fonts than Google Chrome itself has, due to a bug in the Chrome OpenType >sanitizer which rejects CBDT fonts for not having a glyf table. This means that >Chrome will currently only display CBDT fonts that are installed, not ones >loaded by @font-face. > > > >---------- > >This post sent on SVG glyphs for OpenType Community Group > > > >'Chromatic fonts - implementation roundup' > >https://www.w3.org/community/svgopentype/2016/08/15/chromatic-fonts-implementation-roundup/ > > > >Learn more about the SVG glyphs for OpenType Community Group: > >https://www.w3.org/community/svgopentype > > >
Received on Monday, 15 August 2016 17:49:23 UTC