The Home link is created in the template named 'footer.navigation' in
html/chunk-common.xsl. Look for 'home' in that template.
Bob Stayton
Sagehill Enterprises
DocBook Consulting
[EMAIL PROTECTED]
- Original Message -
From: Kari Bourgeois
To: Mauritz Jeanson
Cc: 'docbook-app
I was browsing the web and found archives of the list where a similar
question was asked.
There are a number of non-free and sometimes expensive (most of the
times not multiplatform) tools that support DocBook XML.
Free and multiplatform software that supports DocBook XML are few and
I pe
There is no standard way, it depends on your XSL-FO processor. Look in your
XSL-FO processor doc for an extension to put metadata into the FO in a form
that the processor will put into the PDF.
Bob Stayton
Sagehill Enterprises
DocBook Consulting
[EMAIL PROTECTED]
- Original Message
You meant "Thanks Jirka", of course.
Bob Stayton
Sagehill Enterprises
DocBook Consulting
[EMAIL PROTECTED]
- Original Message -
From: "Dave Pawson" <[EMAIL PROTECTED]>
To: "Docbook-Apps"
Sent: Friday, March 02, 2007 2:36 AM
Subject: Re: [docbook-apps] v5 xinclude
Jirka Kosek wrote
Sorry for not providing more info.
I'm using 1.69 version of the stylesheets (not brave enough to update
yet) and xsltproc to produce the HTML. This produces a navigational Home
link at the bottom of every topic and I'm trying to adjust that.
Along these lines, can anyone recommend a good too
> -Original Message-
> From: Kari Bourgeois
>
> Can anyone tell me how to adjust the target of the home link at the
> bottom of HTML docbook production. Currently, the link goes
> to .html and
> I've been unable to figure out how to change this.
Can you please be a little more specif
Dear list,
is there a way to putt he revnumber into the pdf meta information?
Thanks,
Hinrich
Jirka Kosek wrote:
Dave Pawson wrote:
I'm curious why v5 has separate schemas for the xinclude version?
Normally, you should validate final document after XIncludes are
resolved. DocBook+XInclude schema is there mainly for editors which are
able to guide through editing. Such editors are usua
Hi,
I was following this thread as I was working with image sizing at the time.
I changed the attribute contentheight to contentdepth as per the comments.
This removed a validation error I was receiving (Attribute "contentheight"
must be declared for element type "imagedata"). However, I encounte
Jirka Kosek wrote:
Dave Pawson wrote:
I'm curious why v5 has separate schemas for the xinclude version?
Normally, you should validate final document after XIncludes are
resolved. DocBook+XInclude schema is there mainly for editors which are
able to guide through editing. Such editors are usua
Dave Pawson wrote:
> I'm curious why v5 has separate schemas for the xinclude version?
Normally, you should validate final document after XIncludes are
resolved. DocBook+XInclude schema is there mainly for editors which are
able to guide through editing. Such editors are usually unable to
resolve
I'm curious why v5 has separate schemas for the xinclude version?
regards
--
Dave Pawson
XSLT XSL-FO FAQ.
http://www.dpawson.co.uk
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
12 matches
Mail list logo