Re: [docbook-apps] Website makefiles and xml source arrangement

[Doug du Boulay <ddb@owari.msl.titech.ac.jp>]

Hi Bob,

On Tuesday 02 November 2004 00:59, Bob Stayton wrote:
> Hi Doug,
> You get the message about the current.docid when you use a <sitemap>
> element in the olink database.  When a sitemap element is used, you can 
put
> your output in different directories, and the current.docid is needed to
> compute the path from one directory to the other.  

Ok, thats what I was hoping for.

> It cannot assume that
> the top-level element id is the same as the current.docid.

Do you know of any other ways to figure out what current.docid aught to be 
automatically (I'm trying to learn a bit of XSLT so I don't mind a bit of 
hacking if needed)?

> The database that is automatically generated by webside (named
> website.database.xml) does not include a sitemap element, it just has a
> flat list of documents.  Did you add the sitemap to 
website.database.xml,
> or are you also using a regular olink database that has it?

Yes, I thought a regular olink database might be more general and useful 
so I was working with the target.database.document  file.

thanks again for any insights or suggestions.
Doug

> Bob Stayton
> Sagehill Enterprises
> DocBook Consulting
> bobs@sagehill.net
>
>
> ----- Original Message -----
> From: "Doug du Boulay" <ddb@owari.msl.titech.ac.jp>
> To: <docbook-apps@lists.oasis-open.org>
> Sent: Monday, November 01, 2004 2:09 AM
> Subject: [docbook-apps] Website makefiles and xml source arrangement
>
> > Hi all,
> >
> > I was trying to use Website  and had a couple of problems.
> >
> > Trying to build the website using makefile rules and olinks with an 
olink
> > database I got messages  that I should set    current.docid to resolve
> > the olinks.
> >
> > I am just wondering if there is a way to do that automatically
> > without adding it in the makefile rules?  Can it be deduced from
> > the document  id  of the currently processed document, or does it
> > do that already and I've likely screwed something up?
> >
> > Also:
> >
> > %.html: autolayout.xml
> >         $(ENV) $(PROC) --xinclude \
> >            --stringparam  base.dir  "../html/"  \
> >            --stringparam  autolayout-file "../autolayout.xml" \
> >            --stringparam website.database.document
> > "../website.database.xml" \
> >            --stringparam  target.database.document  "../olinkdb.xml" \
> >            --stringparam  html.stylesheet  "webstyle.css"  \
> >            ...
> >
> > If your source XML webpage documents are not all in the same
> > directory but arranged in sub/sub/sub directories is there someway
> > to set the paths on all the auxilliary xml files so that the %.html 
rule
> > will access the right databse files etc for each source document?
> > Apparently they are all relative to the currently processed xml 
document.
> > How do other folk make this work?
> >
> > Maybe a similar problem, setting html.stylesheet, the html files seems 
to
> > point to the stylesheet in a fixed relative directory (typically "."),
> > rather than to some common global stylesheet. I am not sure if I 
haven't
> > mucked something up.
> >
> >
> > Obviously I could just make a document specific makefile with tailor 
made
> > paths, but its not so elegant.
> >
> > thanks for any advice
> >
> > Doug