On my previous post, I was assuming that MSXML 3.0 was installed and
xmlinst.exe was run. IIRC, MSXML 3.0 is required with XMetaL 2.x install,
but I could be wrong with this one.
The default MSXML parser that comes with IE5 are 2.6, which does not support
the XSLT namespace. It was released long before the W3C recommendation so it
was based on the prototype XSL. Although it is unclear to me at this moment,
I believe that Microsoft purposely set the default installation of MSXML 3.0
to be run in side-by-side mode for compatibility with applications using the
older namespace, although I haven't verified this yet. Whatever the reason
was, running xmlinst.exe is quite annoying, as the user also requires admin
privileges (or "power users," perhaps) to execute it and make the necessary
The macro could be easily re-written to use MSXML instead of XT.Application,
although I haven't tried this yet. And if I use the version-specific progID,
such as MSXML.DOMDocument30, it may render XSLT without having to run
xmlinst.exe, which should save quite a bit of hassle for many people. But
again, I haven't tried this yet.
Installing James Clark's XT parser is an excellent idea, btw. Where can it
P.S. I tried your cookbook styles but IE returned some errors with some of
your templates. You had quite a few named templates that used select="."
attribute, which caused an error with MSXML. Could you look into this? I
checked with the W3C specs and it appears to me that it shouldn't be there.
I realize that you wrote the stylesheet back in July of last year (great
job, btw) so perhaps some specs have changed since then. When I removed all
the select="." that caused errors, the stylesheets worked like a charm.
----- Original Message -----
From: "Fox, Michael" <[log in to unmask]>
To: <[log in to unmask]>
Sent: Monday, June 11, 2001 12:33 PM
Subject: Re: XMetaL Configuration Problem: Page Preview
> Whether or not there is a "problem" with MSXML 3.0 or not, let me
> what I wrote earlier to this list.
> 1. The XMetaL files created for the EAD Cookbook, located on the SAA EAD
> Roundtable web site, were for XMetaL version 1.2. This version utilized
> James Clark's XT software to do a page preview using an XSLT stylesheet.
> 2. With XMetaL 2.0, Softquad changed the default transformation software
> to the MSXML processor. The ead.mcr file- this is the file that drives
> print preview function- that is found in the Cookbook directory will not
> work with this configuration.
> 3. You have three choices.
> a. You can change the default XSLT engine in XMetaL 2.0 to XT. This is
> simple- I described how to do that in an earlier posting.
> b. You can use the MSXML engine that XMetaL expects you to employ as the
> default. The problem with this approach is that you will need to install
> version 3.0 of the MSXML version on your computer. This is not (or wasn't
> the last time I looked) the default version with IE 5.0 or 5.5, both of
> which have version 2.0. You can download and install either version 3.0,
> version 3.0 service pack 1, or a beta (preview) version of 4.0. But
> that's not enough. You must also download and "use the xmlinst.exe
> installer tool to manually replace the older parser with the newer one."
> This reconfigures the Windows registry to enable the newer version.
> c. You can add a stylesheet instruction to the top your document that
> explicitly invoke a particular stylesheet for page preview as the writer
> below describes. However, it is not quite as simple as merely adding the
> stylesheet processing comment given in this message. Unless you have
> updated MSXML as described in the previous option, you will be using
> 2.0 of it, as found in your browser. This may or may not support all the
> XSLT functions you use in your stylesheet. Also, you will have to
> a copy of the ead.dtd and eadbase.ent files, as well as the referenced
> stylesheet, in a directory where you browser can find and parse them
> the transformation will work.
> For all these reasons, I am sticking with using XT which is easy, fast and
> 4. I do not know what Softquad has done with version 2.1.
> Michael J. Fox
> Assistant Director for Library and Archives
> Minnesota Historical Society
> 345 Kellogg Blvd West
> St. Paul, MN 55102-2409
> 651-296-2150 (phone)
> 651-296-9961 (fax)
> [log in to unmask]
> -----Original Message-----
> From: Joo Hang Cha [mailto:[log in to unmask]]
> Sent: Monday, June 11, 2001 1:26 PM
> To: [log in to unmask]
> Subject: Re: XMetaL Configuration Problem: Page Preview
> The only problem with MSXML 3.0 is that it requires to be installed in
> "replace" mode in order to make it transform XML documents with the XSLT
> namespace, rather than working only with the older XSL namespace.
> The problem with the XMetaL Page Preview is associated with the macro.
> you click on Page Preview, the macro script attempts to create an ActiveX
> object with progID called XT.Application.
> XT.Application is the older parser that was used with XMetaL 1.2 and the
> macro was designed for this parser.
> Version 2.x of XMetaL uses MSXML parser, however. Therefore,
> parser is not installed, so the macro returns an error since the object
> not exist.
> One way to get around this issue is to comment out the page preview macro
> script with "//" so that it does not execute.
> In order to transform the EAD documents with a stylesheet, add the
> processing instructions just below <?xml version="1.0"?> at the top of the
> <?xml-stylesheet href="stylesheet.xsl" type="text/xsl"?>
> This tag will instruct IE5 and MSXML to transform the EAD document with
> specified XSLT stylesheet.