Print

Print


We actually took a similar approach by using CSS to mimic the 
navigational features of frames since we wanted to reap the benefits of 
frames but didn't still wanted to be able to transform the document to 
HTML on-the-fly (and couldn't use Saxon with our current XML delivery 
software).  I wrote a paper about this several months ago but got 
stumped on the convoluted javascript required to detect the various 
browsers accurately.  The script currently supports all of the major 
browsers, but not all of them (like Mac's Safari which I haven't been 
able to build in support for at this time). But I think it's worth 
publishing as it stands now.  If anyone is interested, the document is here:

http://staff.washington.edu/carlsonm/beyondframesets.pdf

Stephen Yearl wrote:
> 
> On 10/31/06, *Mark Carlson* <[log in to unmask] 
> <mailto:[log in to unmask]>> wrote (in part):
> 
>  >it isn't so much a stylesheet issue as it is an XSLT
>  >processor issue. 
> 
> Correct. XSLT 1.0 did not have a mechanism for creating multiple output 
> documents from a single XML source. XSLT 1.1 did, and  several XSLT 
> processors extended  the XSLT 1.0 specification to allow one to create 
> multiple outputs.
> 
> Might I suggest that anyone wishing to do this-- and remain standards 
> compliant-- take a look at XSLT 2.0 which explicitly defines 
> xsl:result-document.  A snippet of code producing an XHTML file for each 
> C01, for example _might_ look like:
> 
>  <xsl:for-each select="c01">
> <xsl:variable name="c01_id" select=".//@id[1]"
>  <xsl:result-document href="{$c01_id}.html" method="xhtml" version=" 
> 1.0"  omit-xml-declaration="no" indent="no" encoding="UTF-8"
> doctype-public="-//W3C//DTD XHTML 1.0 Strict//EN"
> doctype-system=" http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
> 
> <!-- HTML markup, and more XSLT here -->
> 
> </xsl:result-document>
> </xsl:for-each>
> 
> Catherine Stollar Peters wrote (in part):
>  > Can anyone think of another stylesheet to transform one EAD
>  > file into multiple HTML files without using Saxon?
> 
> Alas, as far as I know only Saxon 8.x (available in the oXygen XML 
> editor) offers XSLT 2.0 support. Although a quick 'google' did offer 
> this from Altova: http://www.altova.com/products/xmlspy/xsl_xslt_editor.html
> 
> As a caveat XSLT 2.0 is not without its critics, and uptake has been slow.
> 
> HTH,
> 
> St.
> 
> Stephen Yearl
> Systems Archivist
> Yale University Library::Manuscripts and Archives
> 
> 
>     Catherine Stollar Peters wrote:
>      > My institution needs to display some of our larger EAD files as
>     separate
>      > HTML pages but we want to keep the XML file intact.  Looking at
>     the EAD
>      > Cookbook's eadcbs7.xsl and the version sent in the previous email
>     by Amy
>      > MCCrory (thanks, Amy), it seems like they both require Saxon to
>     transform
>      > the XML file.  Can anyone think of another stylesheet to
>     transform one EAD
>      > file into multiple HTML files without using Saxon?  (Our files
>     will be
>      > served up and transformed into HTML on the fly using a stylesheet.)
>      >
>      > Thanks in advance.
>      >
>      >
>      >
>      > Catherine Stollar Peters, Archivist
>      > Harry Ransom Center
>      > The University of Texas at Austin
>      > P.O. Box 7219
>      > Austin, Texas 78713-7219
>      > P: 512-232-4615
>      > www.hrc.utexas.edu <http://www.hrc.utexas.edu>
>      >
>      > -----Original Message-----
>      > From: Encoded Archival Description List [mailto: [log in to unmask]
>     <mailto:[log in to unmask]>] On Behalf Of
>      > Amy McCrory
>      > Sent: Saturday, October 21, 2006 8:20 AM
>      > To: [log in to unmask] <mailto:[log in to unmask]>
>      > Subject: style sheet for long finding aids
>      >
>      > This stylesheet offers a few modifications to the EAD Cookbook's
>      > eadcbs7.xsl.  It addresses two problems inherent in very long
>      > collection descriptions:
>      >
>      > 1. It builds on eadcbs7.xsl 's techniques for splitting the finding
>      > aid into separate HTML pages--one for the collection-level
>      > description, and one for each series level.
>      >
>      > 2. I've removed all the <table> formatting, thereby reducing the
>     size
>      > of the HTML output.
>      >
>      > (It doesn't address the problem Michael stated, of controlling the
>      > width of columns, which various browsers interpret differently.  I'm
>      > guessing percentages instead of pixels would be a good start, though
>      > I've heard there can be problems with that approach too.)
>      >
>      > Additionally, I've substituted divs for frames.  (Thanks to everyone
>      > on this list who sent advice when I asked how to do this several
>      > months ago!)  The Table of Contents <div> has the attribute
>      > "position:fixed", which keeps the TOC onscreen no matter how far you
>      > scroll down the page.  Unfortunately, this is not yet supported in
>      > Internet Explorer.  It works in Opera and in the newest release of
>      > Netscape, though.
>      >
>      > Please feel free to add your own modifications, or to suggest
>      > improvements to mine.
>      >
>      > Amy
>      >
>      >
>      >
>     ----------------------------------------------------------------------
>      > Amy McCrory
>      > Digital Imaging Specialist, Preservation Department
>      > 228 Thompson Library, 1858 Neil Avenue
>      > The Ohio State University Libraries
>      > Columbus, OH 43210
>      > (614) 292-8647
> 
> 

-- 


Mark Carlson
Computer Support Analyst
Special Collections Division
University of Washington Libraries
BOX 352900
Seattle, WA, 98195
(206) 543-1929
http://staff.washington.edu/carlsonm/