Re: [xep-support] SVG DTD bug?

Thanks, David,
Yes, it was a firewall in my case, and I was able to fix it.

But could I make a feature request? Why not ship the SVG DTD, resolver.jar
files, and a small XML catalog, and set up your batch files to use them? I
think you will have fewer perplexed users.

Bob Stayton
Sagehill Enterprises
DocBook Consulting
bobs@sagehill.net

----- Original Message -----
From: "David Tolpin" <dvd@davidashen.net>
To: <xep-support@renderx.com>
Sent: Sunday, November 21, 2004 1:52 AM
Subject: Re: [xep-support] SVG DTD bug?

> Hi Bob,
>
> > 1. Why does your SVG processor fail if it cannot download the W3C SVG
DTD
> > that is specified in the DOCTYPE of some SVG files? I don't think you
need
> > that DTD to render an SVG file, do you? Other processors seem to handle
the
> > SVG file without it.
>
> The SVG DTD is organized in such a way that it puts SVG into proper
> namespace by attaching a proper xmlns attribute to the root element.
> Our SVG processor is necessarily namespace-aware, or it would not
> be able to process svg images inside instream-foreign-object.
>
> > 2. Why does your SVG processor fail to load the W3C SVG DTD when, in
fact,
> > the URL *does* work outside of XEP? I get this error every time I
process a
> > file that references an SVG graphic that has the DOCTYPE:
> >
> > [error] Failed to create image file:/c:/xml/mydocs/test.svg of type null
> > [error] com.renderx.graphics.ImageFormatException:
> > org.xml.sax.SAXParseException
> > : Cannot read from
http://www.w3.org/TR/2001/REC-SVG-20010904/DTD/svg10.dtd
> > (Connection refused: connect)
>
> This is a message from Java's URLConnection.
>
> Im most cases this means that you
>
> 1) have a firewall in your location that prohibits direct connection
> to external resources over http.
> 2) you have an http proxy set up in your location, and settings in
> the browser that let you download the DTD through the proxy
> 3) Java is not set up to use proxy for http connections.
>
> In order for Java to use http proxy, system properties http.proxyHost
> and http.proxyPort must be set appropriately; in my installation it is
>
> java -Dhttp.proxyHost=squid -Dhttp.proxyPort=3128 ....
>
> David Tolpin
> -------------------
> (*) To unsubscribe, send a message with words 'unsubscribe xep-support'
> in the body of the message to majordomo@renderx.com from the address
> you are subscribed from.
> (*) By using the Service, you expressly agree to these Terms of Service
http://www.renderx.com/tos.html
>
>

-------------------
(*) To unsubscribe, send a message with words 'unsubscribe xep-support'
in the body of the message to majordomo@renderx.com from the address
you are subscribed from.
(*) By using the Service, you expressly agree to these Terms of Service http://www.renderx.com/tos.html
Received on Sun Nov 21 17:27:56 2004