- From: Chris Lilley <chris@w3.org>
- Date: Fri, 21 Nov 2014 15:05:53 +0100
- To: Behdad Esfahbod <behdad@behdad.org>
- CC: "Levantovsky, Vladimir" <vladimir.levantovsky@monotype.com>, Sairus Patel <sppatel@adobe.com>, "mpeg-OTspec@yahoogroups.com" <mpeg-OTspec@yahoogroups.com>, Cameron McCormack <cam@mcc.id.au>, <public-svgopentype@w3.org>
Hello Behdad,
Friday, November 21, 2014, 3:24:30 AM, you wrote:
> As promised, here's the proposed addition to the SVG_in_OpenType spec. Under
> 2.2.3 SVG Document Index Entry, before the last paragraph ("For further
> details about the content of the SVG documents..."), add:
> """
> While SVG 1.1 requires [0] that conforming SVG implementations must correctly
> support gzip-encoded [RFC1952] and deflate-encoded [RFC1951] data streams,
> this specification requires that conforming SVG implementations must correctly
> support plain-text and gzip-encoded [RFC1952] data streams only. In any case,
> svgDocLength encodes the length of the encoded data, not the decoded document.
> """
That is slightly odd, as it could be read to mean a superset of SVG
rather than (as was intended) a subset. I suggest this minor
clarification:
While SVG 1.1 requires [0] in addition to plain text encoding that
conforming SVG implementations must correctly support gzip-encoded
[RFC1952] and deflate-encoded [RFC1951] data streams, (etc etc)
> [0] http://www.w3.org/TR/SVG11/conform.html#ConformingSVGViewers
--
Best regards,
Chris Lilley, Technical Director, W3C Interaction Domain
Received on Friday, 21 November 2014 14:06:08 UTC