On Mar 15, 2006, at 15:26, Jeremias Maerki wrote:
> Due to my recent work on changing the way SVG graphics
are loaded
> in FOP
> and a special XML parser/XSLT impl setup I discovered a
potential
> source
> of problems. For example, if you use SAXON 8 as your
XSLT
> implementation
> and use the XSLT output to build up the SVG DOM you
might run into
> problems with attributes: The namespace URI for
attributes will be an
> empty string ("", used by SAX) instead of
null (used by W3C). The
> Batik
> DOM currently doesn't normalize empty strings to null.
It may be
> good to
> eventually do more defensive programming in this area.
It's not just defensive, it's actually required for
conformance to
the DOM: "In programming languages where empty strings
can be
differentiated from null, empty strings, when given as a
namespace
URI, are converted to null." --http://www.w3.
org/TR/DOM-Level-3-Core/
core.html#Namespaces-Considerations
--
Robin Berjon
Senior Research Scientist
Expway, http://expway.com/
------------------------------------------------------------
---------
To unsubscribe, e-mail: batik-dev-unsubscribe xmlgraphics.apache.org
For additional commands, e-mail: batik-dev-help xmlgraphics.apache.org
|