At 11:36 AM 6/30/2006, you wrote:
I probably missing something trivial here.
The part between the square brackets is called the "internal DTD subset".
And unfortunately there's no way in unextended XSLT to handle this gracefully. So no, you're not missing anything.
When forced into the corner, people often use a post-process to (re-)attach this kind of stuff. Alternatively, if you're using Saxon there are extensions that can help (though I can't say off hand if they're comprehensive enough to do the job for you).
If it were me, however, I wouldn't keep these particular NOTATION declarations (along with the declaration and invocation of that external parameter entity) in internal subsets at all, as they're not peculiar to particular documents, but rather (apparently) apply to an entire set of documents. I'd have them in an external subset module, where I could refer to them using the DOCTYPE's SYSTEM identifier. In other words, the thing that calls main.dtd would call a wrapper module containing these declarations and which would call main.dtd in its turn:
<!DOCTYPE book SYSTEM "amended.dtd" >
amended.dtd would look like:
<!NOTATION XML SYSTEM ""> <!NOTATION MIF SYSTEM ""> <!NOTATION TIF SYSTEM ""> <!NOTATION AI SYSTEM ""> <!ENTITY % catalog PUBLIC "-//Siberlogic//ENTITIES V3.0.1//EN" "file:///C:/xml/fips/catalog.pen"> %catalog; <!ENTITY % main SYSTEM "../../System/DTD/main.dtd"> %main;
(Or maybe you could put this module next to main.dtd and adjust the paths accordingly.)
I'd regard this as better layering, and incidentally more accommodating of XSLT's limitations.
Good luck, Wendell
PURCHASE STYLUS STUDIO ONLINE TODAY!
Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!
Download The World's Best XML IDE!
Accelerate XML development with our award-winning XML IDE - Download a free trial today!
Subscribe in XML format