W3C home > Mailing lists > Public > public-svg-wg@w3.org > October to December 2010


From: Cameron McCormack <cam@mcc.id.au>
Date: Sat, 18 Dec 2010 08:05:31 +1300
To: public-svg-wg@w3.org
Message-ID: <20101217190531.GB31176@wok.mcc.id.au>
Hello team.  Should conform-viewers-02-f really pass?


Since data: URIs can’t provide a Content-Encoding header like HTTP
responses can, it seems like a UA should try to decode the gzipped data
as XML data and should fail.  The Conformance appendix says this:

  When an SVG viewer retrieves compressed content (e.g., an .svgz file)
  over HTTP, if the "Content-Encoding" and "Transfer-Encoding" response
  headers are missing or specify a value that does not match the
  compression method that has been applied to the content, then the SVG
  viewer must not render the content and must treat the document as
  being in error.

so it looks like the intention there is to point out that gzipped data
is not SVG itself – the compression is a step afterwards.

I guess this is kind of related to the thread Erik started recently
about loading svgz files locally.

Cameron McCormack ≝ http://mcc.id.au/
Received on Friday, 17 December 2010 19:06:09 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:29:44 UTC