- From: Dr. Olaf Hoffmann <Dr.O.Hoffmann@gmx.de>
- Date: Fri, 7 May 2010 11:35:43 +0200
- To: www-smil@w3.org, www-svg@w3.org
Jack Jansen: > Olaf, > from the SMIL Animation side of the picture escaping can be done with > percent-encoding. But that leaves the question of when the SVG renderer > will decode the percent escapes. The URI definition > <http://tools.ietf.org/html/rfc3986#section-2.4> suggests that it is done > after splitting the URL on delims and subdelims, so that would mean it > would be too late. This was my impression too, because it appears within the part of the fragment identifier. Because this is presumably the only case, where such a conflict appears in SVG, the SVG-WG could add some hint for authors and implementors for this case either already to the SVG 1.1 second edition, as a proposed errata or at least to an new version ... > > In SMIL there may be a workaround using SMIL State, but I don't think > that's allowed in SVG. And, indeed, in SMIL the href attribute isn't > animatable (but it may contain SMIL State {attribute value template} > constructs). But in SMIL you could also break open the values animation > into a sequence of <set> animations. > Because for an arbitrary use of SMIL animation the appearence of a semicolon within a values list item cannot be excluded (not just in IRIs), it might be a good idea, that the SMIL animation chapter defines how to escape a conflicting semicolon in general. Unfortunately I did not discover this before SMIL3 became a recommendation ... Olaf
Received on Friday, 7 May 2010 09:40:18 UTC