- From: Leonard Rosenthol <lrosenth@adobe.com>
- Date: Thu, 23 Feb 2012 04:14:33 -0800
- To: Cameron McCormack <cam@mozilla.com>
- CC: Edwin Flores <eflores@mozilla.com>, Sairus Patel <sppatel@adobe.com>, "public-svgopentype@w3.org" <public-svgopentype@w3.org>
It's that the current fill paint or stroke paint isn't compatible with SVG - so that the SVG renderer couldn't do the drawing. Consider PDF, which supports a variety of colorspaces that SVG does not. For example, the current fill "paint" might be a spot color (e.g Pantone or Toyo). How would I pass that down to the SVG system? Obviously, I can't. Which is why it the SVG has to pass back the shape/mask back up to the font engine and then back up to the rendering system. Leonard -----Original Message----- From: Cameron McCormack [mailto:cam@mozilla.com] Sent: Wednesday, February 22, 2012 10:24 PM To: Leonard Rosenthol Cc: Edwin Flores; Sairus Patel; public-svgopentype@w3.org Subject: Re: Two flavors of glyphs: color-specifying and color-inheriting Leonard Rosenthol: > Unfortunately such a model doesn't work when using the font in a > non-Web context. > > Consider using this font inside of MSWord or Adobe InDesign or a PDF > document. Those applications all have graphics models which don't map > 100% to the SVG model NOR do you have access to those attributes to be > able to use them (even if they could map). I don't understand this, can you explain a bit further? Is it that these models do not have the concept of a current fill paint and current stroke paint? Is it that they would normally set up a path using the text, and then fill and then stroke that path?
Received on Thursday, 23 February 2012 12:15:06 UTC