Hi Anna,

method="html" should also come in your xsl:output.

I'm not sure that you will be able to do what you want to do strictly with
browser-based xslt processing.  It seems to me that there is no way to pass
a URL parameter for use in the XSL stylesheet, if that is what $file is.
You should consider generating static HTML or using javascript/ajax to
display the parts of the finding aid that you want depending on a URL
parameter.  The latter is actually a pretty elegant solution.


On Wed, Mar 31, 2010 at 11:05 AM, Anna Kresmer <[log in to unmask]> wrote:

> Thanks a lot! I moved the doctype-public attribute to the xsl:output
> element and that has made that error message go away. I also removed the
> reference to the Saxon name space, which does not appear to have caused a
> problem. The bit of code now reads like this:
> <xsl:stylesheet xmlns:xsl=""
> version="1.1">
> <xsl:strip-space elements="*"/>
>  <xsl:output encoding="ISO-8859-1" doctype-public="-//W3C//DTD HTML 4.0
> Transitional//EN" method="html"/>
> However, fix one error and another one makes itself known. I now have a
> pair of errors linked to 2 xsl:document attributes. The lines of code look
> like this:
> <xsl:document method="html" href="{$file}.html">
> <xsl:document method="html" href="{$file}recordgrp{$recordgrp}.html">
> In both cases, there is a jagged red line under the tml">. Each of these
> lines of code are part of sections that instruct the stylesheet to create
> a new page (either for the collection-level description or for each series
> of the finding aid).
> The error codes linked to each of them look like this:
> Description: Attribute @method is not allowed on element <xsl:document>
> Description: Attribute @href is not allowed on element <xsl:document>
> I do not have a clue what to do with this one. Any ideas?
> Sorry to take up so much time,
> Anna