Thanks Bob,
I'm pulling the stylesheets through docbkx-tools without actually specifying
the version directly in my projects. Perhaps I could overload the templates in
my customization file for chunked output, but it looks a lot simpler to wait
and to continue copying the CSS file to the
HI Bob,
if in epub3/epub3-element-mods.xsl you change the current generate.toc
param definition to:
xsl:param name=generate.toc
article toc
book toc,title,figure,table,example,equation
/xsl:param
(i.e. just add article toc)
Everything works correctly also for articles, so the patch is very
Nick, your code puts a number on the title page:
xsl:when test=$pageclass = 'titlepage'and $sequence = 'first'
fo:page-number!-- nop --/fo:page-number
/xsl:when
I see you have a comment of !--nop--. But the empty element
fo:pagenumber/ inserts a page number. I think you want:
xsl:when
hi,
I wonder if there is already a tool out there to visualize a DocBook
document as a treemap.
I came across some interesting research on how one can visualize
changes between two treemaps that would be useful to monitor changes
in a DocBook document: create the treemap today, create a new one
Hi Tim.
You might take a look at diffxml. http://diffxml.sourceforge.net/ I think it
looks promising. But I am not sure if there is some kind of html visualizer
available.
cheers,
/frank
9 feb 2012 kl. 16.22 skrev Tim Arnold:
hi,
I wonder if there is already a tool out there to visualize
Paul,
Thanks for your response, of course your observation is correct, but
unfortunately it it had no effect either. I previously had the following:
xsl:when test=$position='centertop'
xsl:if test=$pageclass != 'titlepage'
fo:page-number/
/xsl:if
/xsl:when
But this has no effect, by
Hi Nick,
I think your footer.content template needs to take into account your new page-master
name:
xsl:choose
xsl:when test=$pageclass = 'coversequence'
!-- nop --
/xsl:when
etc.
Bob Stayton
Sagehill Enterprises
b...@sagehill.net
- Original Message -
From: Wood,
In this section of my book:
http://www.sagehill.net/docbookxsl/ModularDoc.html#XincludeSelect
I address that problem with this sentence:
For selections based on id, the included document must have a DOCTYPE declaration
that correctly points to the DocBook DTD. It is the DTD that declares that
Hi Giuseppe,
The DocBook developers are interested in making DocBook output more accessible. If you
manage to create customizations that improve accessibility and are willing to share
them, I could incorporate the changes into the base stylesheets for future releases.
Any changes that appear
Anyone here interested in joining our documentation group as a tech
writer with a focus on writing docs for the Oracle Linux product?
If so, have a look at my blog under http://blogs.oracle.com/mysqlf/. The
latest post has links to the official, detailed job description.
For questions, you
Bob:
Thank you very kindly for the reply. I should have included the entire file in
the example given,
it does indeed have a dtd, exactly as shown in your book:
?xml version=1.0 encoding=UTF-8?
!DOCTYPE chapter PUBLIC -//OASIS//DTD DocBook XML V4.5//EN
Gregorio,
You might look at adding --nonet and --novalid to your xsltproc command
line if they are not there already.
You didn't mention the command line options that you are invoking XSLTPROC
with.
Regards,
Dean Nelson
In a message dated 2/9/2012 10:17:57 A.M. Pacific Standard Time,
That is the problem, but I'm not clear why the DTD cannot be loaded. It
certainly resides at that web address.
I would try setting up an XML catalog to redirect the URL to a local copy of
the DTD. That would be faster than web access too.
Bob Stayton
Sagehill Enterprises
b...@sagehill.net
Bob, Dean.
Thank both of you for the help here!
I wound up copying the dtds locally and pointing to the local copy with the
--nonet option worked!!
I am not really fond of doing it this way, and it would require modifying the
DOCTYPE statement in every single doc.
So I am thinking that
Hi Bob,
nice to know someone else is interested in accessibility.
What scares me about a new customization layer is the scale of the
whole thing. I strongly suspect I'll have some big surprise down the
road, so I confess I am thinking about some python postprocessing
hacking on already created
I had to support accessibility requirements in the XHTML output in the
webhelp format. I found that the table cell customizations were the
most complicated.
I posted the XSL customization I use in the DocBook cookbook here:
http://wiki.docbook.org/HtmlTableAccessibility
Peter
On Thu, Feb 9,
Hi Benjamin,
It's actually not that hard, as long as you already have a customization for
other things. If you have, then you could add the following to your
customization. For example, if you want red text:
xsl:template match=d:phrase[@role='red']
fo:inline color=red
17 matches
Mail list logo
