That was my thought when I first looked at the system...
There are a number of options that would provide cross platform
support and more access to the parser/transformation engine, for
example I am unable to access the message buffer of the MSXML parser.
Cheers
Luke
2008/6/24 bryan rasmussen <rasmussen(_dot_)bryan(_at_)gmail(_dot_)com>:
Actually I was just wondering what was the reason for using Python's
Win32 libraries to allow you to invoke MSXML as opposed to other xsl-t
implementations for python that would be cross-platform?
Cheers,
Bryan Rasmussen
On Tue, Jun 24, 2008 at 5:55 PM, Luke Stedman
<luke(_dot_)stedman(_at_)gmail(_dot_)com> wrote:
Thanks for all the comments guys.
When Andrew pointed out the simpler solution I decided to do it the
xsl/include way instead.
It is a lot easier than using the DTD's.
Cheers
Luke
2008/6/24 Wendell Piez <wapiez(_at_)mulberrytech(_dot_)com>:
Luke,
At 10:09 AM 6/24/2008, you wrote:
Thanks Martin,
The fix worked perfectly.
That's cool, but puzzling, since your syntax is unorthodox and shouldn't
work in a conformant XML parser. It could be you are getting your XSLT to
parse now, but how those external DTDs are being used would be a mystery.
2008/6/24 Martin Honnen <Martin(_dot_)Honnen(_at_)gmx(_dot_)de>:
Luke Stedman wrote:
When the dtd's are defined in the XSL file:
<!DOCTYPE xsl:stylesheet [
<!ENTITY SYSTEM "./det_1.dtd">
<!ENTITY SYSTEM "./det_2.dtd">
]>
Here you have declared a DTD as an internal subset (the bracketed structure
within your DOCTYPE declaration), which in turn declares two entities. But
those entities are neither general nor parameter entities. Indeed they're
not entities at all, since they don't have names, just system identifiers
for files.
If you mean to include two DTDs as modules of the DTD in your internal
subset, you need parameter entities, plus a parser that will support them.
What's more puzzling is why you want to do this. If you have global variable
declarations in your XSL which you wish to factor out of the main
stylesheet, xsl:include is easy enough without getting you into the
intricacies of entity declaration and use. Is there any reason you can't
simply use xsl:include?
Cheers,
Wendell
======================================================================
Wendell Piez
mailto:wapiez(_at_)mulberrytech(_dot_)com
Mulberry Technologies, Inc. http://www.mulberrytech.com
17 West Jefferson Street Direct Phone: 301/315-9635
Suite 207 Phone: 301/315-9631
Rockville, MD 20850 Fax: 301/315-8285
----------------------------------------------------------------------
Mulberry Technologies: A Consultancy Specializing in SGML and XML
======================================================================
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail:
<mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail:
<mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail:
<mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--