[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [docbook-apps] Changing the filenames exported from the chunk .xsl?
Hi Charlie, There is a utility stylesheet maketoc.xsl that is included in the DocBook XSL distribution that generates a structured TOC that might suit your needs. Normally it is used to precisely control chunking, but you could possibly use it in your application. See the section titled "Manually control chunking" in: http://www.sagehill.net/docbookxsl/Chunking.html#ControllingChunks Bob Stayton Sagehill Enterprises DocBook Consulting email@example.com ----- Original Message ----- From: "Charlie Hubbard" <firstname.lastname@example.org> To: "Webmaster" <Webmaster@comtrol.com> Cc: <email@example.com> Sent: Monday, July 10, 2006 10:46 PM Subject: Re: [docbook-apps] Changing the filenames exported from the chunk .xsl? > Well I've read over all the information you included (thanks!), but I > don't see how I can do what I wanted to without customizing the XSL > tempaltes in some way. My last email was probably not all that clear. > Sorry it was hard to read. :-) > > The trouble I'm having is that docbook wants to compile the pages into > XHTML so it needs all that information at compile time. I'm trying to > combine information at runtime that is not available at compile time > of the docbook XML. To do that I have to parse the XHTML at runtime > and add my information to the compiled XHTML that the docbook XSL > outputs. I need something like what manifest.xsl does today, but a > little more structure (maybe as XML) to identify what page is the > start and which page is next and previous given the name of a page, > etc. How would I modify manifest templates to output those > relationships? > > Charlie > > On 7/10/06, Webmaster <Webmaster@comtrol.com> wrote: >> Hi. >> >> There is a lot of flexibility in using the chunking stylesheets. I'm >> sure >> most of the problems can be addressed by setting the options you need. >> Take >> a look at: http://docbook.sourceforge.net/release/xsl/current/doc/html/ >> (look under chunking) >> >> >> The name of the "next page" really depends on what level you are >> chunking. >> Are you chunking at the chapter level? then each page will be ch01, >> ch02, >> ch03, etc. if you are chunking at chapters and sections, then you'll >> also >> have pages named for each section. To control this when things are >> chunked, >> look for "generate.toc" at the link above. You can enable navigation on >> your chunked pages, so that each page will have a "next" and "prev" >> link, as >> well as a link to the toc. >> >> The other option is you can use the website stylesheets, which will >> create >> expandable navigation for you, and you can modify the look of the site >> using >> the stylesheet templates. I was able to create a entire portion of our >> site >> based on docbook, and was able to modify the stylesheets so that it >> completely integrates with the rest of the site. more information on >> that >> can be found here: >> http://www.sagehill.net/docbookxsl/Website.html and >> http://docbook.sourceforge.net/release/website/example/index.html >> >> >> LN >> >> > -----Original Message----- >> > From: Charlie Hubbard [mailto:firstname.lastname@example.org] >> > Sent: Monday, July 10, 2006 1:30 PM >> > To: email@example.com >> > Subject: [docbook-apps] Changing the filenames exported from the >> > chunk.xsl? >> > >> > >> > Hi, >> > >> > I'm trying to build a platform for displaying docbook in HTML. The >> > statis HTML won't work for me. Right now I'm using the XSL >> > stylesheets to export docbook to XHTML. The problem is that my >> > platform doesn't really understand anything about the URLs that >> > docbook exports. So if I'm displaying ch01.html I have no idea what >> > the next page is. >> > >> > Is there a way to alert the algorithm to the XSL so that it will chunk >> > something like page1.html, page2.html, etc? I also need a way to >> > figure out which file is the TOC too. Something like if my XSL >> > customizations would export a toc.html file for the book. >> > >> > If this is too hard what about creating a XSL customization that could >> > write out a sort of catalog file that could answer these questions for >> > me. For example, say I chunk a book into several HTML files, and part >> > of the output would include a catalog.xml file that would list the >> > table content's filename, the html filenames in sequential order or >> > something like that. >> > >> > Thanks >> > Charlie >> > >> > --------------------------------------------------------------------- >> > To unsubscribe, e-mail: firstname.lastname@example.org >> > For additional commands, e-mail: >> > email@example.com >> > >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: firstname.lastname@example.org > For additional commands, e-mail: email@example.com > > >