- From: Sairus Patel <sppatel@adobe.com>
- Date: Tue, 16 Aug 2016 21:43:32 +0000
- To: Chris Lilley <chris@w3.org>, "public-svgopentype@w3.org" <public-svgopentype@w3.org>, Cameron McCormack <cam@mcc.id.au>, Jonathan Kew <jfkthame@gmail.com>
I’d also heard of a Firefox bug in which unitsPerEm is assumed to be 1000. Could Jonathan, Cameron, or someone else at Mozilla please confirm that this is still a known limitation of Firefox’s OT-SVG impl? Knowing that would help untangle the issues surfaced by Chris’ post. (Plus, it would be good information for font developers.) Thanks, Sairus -----Original Message----- From: Chris Lilley <chris@w3.org> Organization: W3C Date: Monday, August 15, 2016 at 3:42 PM To: "public-svgopentype@w3.org" <public-svgopentype@w3.org> Subject: Re: 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 3:43 PM > > >On 2016-08-15 20:48, Sairus Patel wrote: >> 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. >Yes, I just noticed this by accident and thought it merited a post. >> 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]. >It isn't clear to me either. LapisLegit is not the only font to exhibit >this. I noticed it first in emojione, which has a related bug: > > I think it may be because of the use of viewBox and arbitrary world >coordinates, rather than using coordinates appropriate to the unitsPerEm >value. > >-- >Chris Lilley >@svgeesus >Technical Director, W3C Interaction Domain > >
Received on Tuesday, 16 August 2016 21:44:03 UTC