W3C home > Mailing lists > Public > public-svgopentype@w3.org > February 2012

Re: Two flavors of glyphs: color-specifying and color-inheriting

From: Cameron McCormack <cam@mozilla.com>
Date: Mon, 27 Feb 2012 09:43:32 +1100
Message-ID: <4F4AB594.8000506@mozilla.com>
To: Leonard Rosenthol <lrosenth@adobe.com>
CC: Edwin Flores <eflores@mozilla.com>, Sairus Patel <sppatel@adobe.com>, "public-svgopentype@w3.org" <public-svgopentype@w3.org>
Cameron McCormack:
>> I think in our SVG-in-OpenType spec we can just define how these
>> input paints get translated into SVG paint values

Leonard Rosenthol:
> No, you cannot do that!
>
> You are thinking about a "Web" or "Screen" only world - but OpenType
> is used EVERYWHERE!   Think about all the places that you see fonts
> used that aren't working in an (s)RGB world or where the final output
> isn't a "bit buffer".  The most obvious, and common, being a physical
> printer.  Printers are CMYK (or CMYK+other) inks being placed onto a
> physical media.  How do you expect your SVG renderer to know what to
> do in that case??  There is no "bit buffer" for it to render into.
> Also consider other hardware devices, perhaps even in monochrome
> devices such as teletypes, billboards, scrolling text signs, etc..

That's why I talked about SVG Color, with which you can represent CMYK 
colours.
Received on Sunday, 26 February 2012 22:44:12 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Sunday, 26 February 2012 22:44:13 GMT