[
https://issues.apache.org/jira/browse/FOP-1747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15392862#comment-15392862
]
Glenn Adams commented on FOP-1747:
----------------------------------
Effectively, FOP/BATIK is doing what you have (implicitly) asked. By specifying
a DTD PUBID, you are effectively asking to validate the content using that
specific DTD resource.
| 1. Is there any way to avoid the DTD fetch without modify ApacheFOP?
Have you tried removing the PUBID or the DOCTYPE decl?
| 2. If not, is the right thing top do to bundle the DTD with ApacheFOP and use
a custom EntityResolver to read it?
That is one possibility, but I would probably oppose it (baking in a specific
DTD). Better to have the FOP application/client supply its own entity resolver
to override the origin of the DTD.
| 3. Is this related to: https://issues.apache.org/jira/browse/BATIK-1018?
No.
> FOP should provide SVG DTD
> --------------------------
>
> Key: FOP-1747
> URL: https://issues.apache.org/jira/browse/FOP-1747
> Project: FOP
> Issue Type: Improvement
> Components: image/svg
> Affects Versions: trunk
> Environment: Operating System: All
> Platform: All
> Reporter: J.Pietschmann
>
> Currently, DTDs in external SVG graphics are loaded from their standard
> location on the Net. This may cause problems for machines not connected
> to the Net.
> FOP should provide an infrastructure which loads the standard SVG DTDs
> (and possibly other standard DTDs) from a local location.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
