The newer Versions of Saxon (if you use the freeware licence) are not usable
for namespace-aware scripts. Are there any parts in your xslt, which uses
the default namespace (there are no namespace-suffix in your Xpath (for
If you use the default namespace in your xslt Skripts just add a namespace
(for example: ead:c/ead:did/ead:unittitle)
I had to change many of our XSLT scripts on changing to a newer Saxon than
6.x because the freeware version does not run namespace-aware xslts.
If you need assistance, please feel free to contact me
startext Unternehmensberatung GmbH
Tel: (0228) 9 59 96-31
Fax: (0228) 9 59 96-66
Geschäftsführer: Paul Bantzer
Handelsregister: Amtsgericht Bonn HRB 2741 Sitz der Gesellschaft: Bonn
Von: Encoded Archival Description List [mailto:[log in to unmask]] Im Auftrag von
Michele R Combs
Gesendet: Freitag, 10. Oktober 2008 21:39
An: [log in to unmask]
Betreff: EAD to HTML, Saxon, and meta tags
Something very weird is going on and I hope someone can tell me why. We've
been using an adapted eadcbs6.xsl stylesheet for upwards of 2 years with no
problems. We're using saxon to run it to produce HTML from our EAD.
Earlier this week (at the request of our IT department) we switched to the
latest version of Saxon, due to security concerns with the Java Virtual
Machine required by our older version of Saxon. We tested it, everything
However, I have just discovered that for some reason with the new version of
Saxon (184.108.40.206, I believe -- the Java version, not the .NET version) the
entire section in eadcbs6.xsl where the <meta> tags are generated (roughly
line 225 on) produces nothing!! This is the section of code starts with
"<!-- Generates HTML meta tags that are inserted into the HTML ouput -->"
So where our output HTML used to include for example:
<meta http-equiv="Content-Type" name="dc.title" content="George William
Curtis Letters"> or
<meta http-equiv="Content-Type" name="dc.subject" content="Journalists,
there is now zip, nada, bupkis.
I tested it by running some EAD files through both the old and the new
version of Saxon and comparing the output, and quite clearly it's being
caused by the new Saxon since that's the only variable. I don't think it
has to do with the saxon:omit-meta-tag attribute, as that seems to apply
only to the first one, the one that specifies the file type as text/html.
Does it have something to do with this saxon being XSL2.0? Our stylesheet
is still XSL1.0 and saxon throws up a warning about that, but the
transformation completes successfully so I figured it didn't matter.
Special Collections Research Center
Syracuse University Libraries
222 Waverly Ave.
Syracuse, NY 13244
[log in to unmask]