On 09/22/2011 08:49 PM, Bob Stayton wrote:
Hi Chris,
Regarrding your first question, you can set the stylesheet param named
'generate.toc' to empty to turn off the TOC chunk. You will still get
the NCX toc.
I noticed the same issue with customizing the epub 2 stylesheet. If
your
On 23 Sep 2011, at 07:30, davep wrote:
On 09/22/2011 08:49 PM, Bob Stayton wrote:
Hi Chris,
Regarrding your first question, you can set the stylesheet param named
'generate.toc' to empty to turn off the TOC chunk. You will still get the
NCX toc.
I noticed the same issue with customizing
Hi,
On Thu, Sep 22, 2011 at 11:30 PM, davep da...@dpawson.co.uk wrote:
Since the toc is never needed (the ncx supplants a toc), would it make sense
to delete the call to generate it such that annoyance is removed?
Many publishers deliberately include an HTML TOC in their EPUB
documents. An
Hi Jason,
No, there is nothing you can put in the text attribute value that will generate
a new line that shows up in your displayed output. Inserting a #x0A; will
insert a new line in the output file, but in neither HTML nor XSL-FO is such a
line break character formatted as a line break.
Hi Mike,
It seems that the para element is an exception for using that mode because it also has
the feature of passing along a role attribute as a class attribute. If the para in
question has a role attribute (of any value) and the $para.propagates.style is set to
1 (the default), then your
Hi Mike,
When you run the FO process, the error output should have shown something like
this:
Element collabname in namespace '' encountered in collab, but no template
matches.
The error should also have shown up in red on the title page because it seems the FO
stylesheet does not have a
Hi Lars,
The short answer is no, the stylesheets don't do anything with link
rel=canonical. The reference is to the Google webmaster site. Is this
feature specific to Google?
DocBook XSL does support customization of the head element by customizing the
utility template named
Which XSL-FO processor are you using? I'm guessing those error messages are coming
from the XSL-FO processor and not the XSL stylesheet.
Setting draft.mode to anything but 'no' causes the stylesheet to load into the XSL-FO
file the extra page-masters that are needed for displaying the draft
Hi Bob,
thanks for the hint. If I read
http://www.sagehill.net/docbookxsl/HtmlHead.html correctly it does not
contain an example for accessing information from the document. But its good
to know and I hope once I get more familiar with custom templates I will
find out how to do it.
Thanks and
