On 12/03/2015 03:07 PM, Shane McCarron wrote: > Yeah - I was going to use theirs but there was no parameter to get > SVG output. So I cloned the repo, added a URI option, and deployed > it. I think we should be using SVG output in the specs (so the specs are self-contained when it comes to W3C publishing, and meet our accessibility needs). We can't have normative content in W3C specs linking to PNG images on an open source community run proxy server. Another option is to check in PNG images, but I'm a -0.5 to this because we shouldn't be checking in stuff that can be generated at page-view time (and can be converted to SVG so it can be placed directly into the documents we're creating). -- manu -- Manu Sporny (skype: msporny, twitter: manusporny, G+: +Manu Sporny) Founder/CEO - Digital Bazaar, Inc. blog: Web Payments: The Architect, the Sage, and the Moral Voice https://manu.sporny.org/2015/payments-collaboration/Received on Thursday, 3 December 2015 22:48:39 UTC
This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:43:12 UTC