files

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

files

Bruce D'Arcus
Here's another minor issue:

In my current approach, the raw bibliographic collection is regenerated
from the database every time the transformation is run.  This may not
always be a good idea, particularly in a collaborative context.

So, in the OOoBib project we would like to be able to optionally save
out the bib file and embed it in the file wrapper.  That way, if User X
sends their document to User Y, the latter can import any missing
records into their local DB (notwithstanding any potential
complications with IDs).  Other (DocBook, TEI, etc.) users might want
that functionality too (in most cases, through a separate file, though
I suppose in WordML that data could be embedded in the main document
somehow?).

Anyway, something as simple as the below might work, where if one is
working with OOo, the default is perhaps "bibliography.xml" (since that
file will always be unique within a file wrapper).   Here I have a
top-level parameter to specify the file name.

    <xsl:template match="/">
      <html>
        <head>
          <title>Testing</title>
        </head>
        <body>
          <div id="content">
            <div id="main-content">
              <xsl:apply-templates/>
            </div>
            <div id="bibliography">
              <xsl:copy-of select="$formatted-biblist"/>
            </div>
          </div>
        </body>
      </html>
      <xsl:if test="$bibout">
       <xsl:result-document href="{$bibout}">
         <xsl:copy-of select="$raw-biblist"/>
       </xsl:result-document>
      </xsl:if>
    </xsl:template>

I suppose it might also make sense to have a fallback where if for some
reason the db isn't available, the stylesheets could use this external
file for the data?

Bruce



Loading...