error message: SAXParseException: An exception occurred!

[Scott Prentice]

Hi Wim...

I can't say for sure .. but from what I've seen I think that FM9's 
attempt to enable the ability to work with http-based files has gone a 
bit overboard. As far as I can tell, if the DTD is specified with an 
http reference, FM9 ignores the public ID and its association to a 
structured app, and actually downloads the DTD from the remote location. 
Unfortunately, even if this was a good idea, it doesn't do the job 
properly and doesn't download the MOD files.

The only "fix" I know of is to change the DTD specification to be just 
the DTD filename. This should work fine with most editors assuming the 
public ID is defined in the catalog and maps properly to a local DTD.

Hopefully someone else will have a better answer .. perhaps there's a 
switch that tells FM to use the public ID. This worked fine in FM8.

Cheers,

...scott

Scott Prentice
Leximation, Inc.
www.leximation.com
+1.415.485.1892



Wim Hooghwinkel - idtp wrote:
> Framers,
>
> I posted this before but so far no response and I didn't succeed in
> resolving it.
>
> Opening an XML file in FM9. XML file USES Public DTD declaration: 
> <?xml version="1.0" encoding="UTF-8"?><!DOCTYPE book PUBLIC "-//OASIS//DTD
> DocBook XML V4.5//EN"
> "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd">
>
> Then an error report in FM comes up: 
> XML Read Report Log 
> XSLT Processor Messages 
> SAXParseException: An exception occurred! Type:Could not open external
> entity 'C\Documents and Settings\kaiijn\AppIication
> Data\NetLibCAche\c696803b24573f4b8 1 35d3caf 7bbadea\dbnotnx.mod', 
> Error in XSL transformation. Stopped file opening. 
>
> In the FrameMaker application an XSLT is run on the XML before it is passed
> on to FrameMaker itself. What seems to happen now is that it (The Parser?)
> makes a local copy of the DTD in the user's folder. But it only copies the
> main DTD file (docbookx.dtd) and not the .mod files. When we take out the
> XSLT, the XML opens fine (but with errors because the XML is not valid,
> that's why we need the XSLT). 
>
> So, I'm wondering: why does FM/the parser make a local copy of the DTD - and
> how comes it doesn't take the complete set. FrameMaker itself knows where to
> find the DTD (if we skip the XSLT - no error).
>
> We don't want to use a local DTD declaration because the XML files will go
> to an external client. In fact, the XSLT adds a local DTD declaration to a
> modified DTD. 
>
> Any ideas how to solve this?
>
>
> Kind regards, vriendelijke groet,
> Wim Hooghwinkel
> iDTP - Technical Communication Consultant
> Adobe Certified Expert (ACE) in FrameMaker / NLDITA 2010
> tel. +31652036811
> Skype wimhooghwinkel
> Twitter @idtp @NLDITA
> info at idtp.eu 
> www.idtp.eu
> www.nldita.nl
> FrameMaker support: framemaker at idtp.eu
>
>
>
>
>