Subject: Re: [docbook-apps] dbhtml-include paths & turning them all off?
You are right. I am doing single-pass profiling. By the way, after thinking about this issue some more (but not actually trying anything), I've pretty sure I can do what I want with XSL. Anyway, it will be a good learning exercise for me. Robert On Wed, Dec 22, 2010 at 8:37 PM, Bob Stayton <email@example.com> wrote: > Hi Robert, > References relative to the local document directory work for me. Are you > doing single-pass profiling by any chance? > > The template uses this line to load the file: > > <xsl:variable name="content" select="document($href,/)"/> > > The "/" after the comma means to take the root of the current document as > the base url. The processor uses that to get the current directory for > relative paths. When you do single-pass profiling, the content is saved > into a node-set, which has no current directory. > > Bob Stayton > Sagehill Enterprises > firstname.lastname@example.org > > > ----- Original Message ----- From: "Robert Nagle" > <email@example.com> > To: <firstname.lastname@example.org> > Sent: Wednesday, December 22, 2010 6:07 AM > Subject: [docbook-apps] dbhtml-include paths & turning them all off? > > >> Ok, here's another "why" question. >> >> I occasionally need to add outside HTML fragments to my HTML output. >> >> I notice that the path to the file is relative to the docbook XSL you >> are using, not the project directory. So >> <?dbhtml-include href="fragment1.html"?> would work only if >> fragment1.html is directly inside your docbook XSL. >> >> Which is a pain -- especially if you need to move the project somewhere >> else. >> >> I guess I can create a folder named fragments one directory above the >> XSL directory (so that the file reference is the same regardless of >> which XSL you use). >> >> But I was wondering: How can my XML parser (Saxon) know to handle >> xincludes and not know how to look for HTML fragments in the same >> directory? >> >> Also: is there a way to "turn off" all dbhtml-includes in your >> customization layer. (I'm assuming that profiling does not work--!?) >> >> for now, I can simply substitute a real fragment1.html file with a >> blank fragment1.html to turn them off. But it would be nice not to >> have to remember that all the time. >> >> Robert >> >> >> >> -- >> Robert Nagle >> 12777 Ashford Point Dr #1417 >> Houston, Texas 77082 >> 713 893 3424 >> http://www.robertnagle.info >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: email@example.com >> For additional commands, e-mail: firstname.lastname@example.org >> >> >> > > -- Robert Nagle 12777 Ashford Point Dr #1417 Houston, Texas 77082 713 893 3424 http://www.robertnagle.info