Hi Bob, thanks for your kind reply!
Bob Stayton wrote:
As you found out, the body of a xsl:call-template can only take
xsl:with-param children, not any other content such as that generated by
xsl:apply-imports.
The basic problem is that this template:
was not written to accept the hot t
Hi Sam,
As you found out, the body of a xsl:call-template can only take
xsl:with-param children, not any other content such as that generated by
xsl:apply-imports.
The basic problem is that this template:
was not written to accept the hot text as a parameter. Instead, you should
look a
I have to create a page-master for legal notice-only. In the page sequence it
appears after the default titlepage.
But, despite spending long time reading the customization section on TDG5, I
am stuck at 2 places:
1) The pages (recto & verso) are being generated, but they always turned
empty.
2)
Hi Maine,
I haven't had a chance to trace through your example in detail, but I will
mention a couple of things you can try.
1. A sitemap is used in a target database to generate *relative* paths between
output files in different output directories. In your case, one of your
baseuri attribute
[input] [input] [input] [input]
YAHOO.Shortcuts.hasSensitiveText = false; YAHOO.Shortcuts.sensitivityType
= []; YAHOO.Shortcuts.doUlt = false; YAHOO.Shortcuts.location = "us";
YAHOO.Shortcuts.lang = "us"; YAHOO.Shortcuts.document_id = 0;
YAHO
Geraint North wrote:
> I'd also appreciate some guidance as to how I should start - should I
> take an existing (e.g. HTML) set of stylesheets, or just write my own
> from scratch? I've done a lot of customisation of the HTML and XSL-FO
> stylesheets, so I have a pretty good idea what's involved
Thanks for that - I'd just started investigating the DocBook -> HTML -
> Wiki route, and that seems to work well. In particular, the
HTML::WikiConverter perl module seems to do pretty much what I want,
although it leaves a lot of FONT and DIV tag hanging around that
screw up the Wiki unles
If you tried to purchase the PDF version of the 4th Edition of DocBook XSL:
The Complete Guide from my website between 9 October and today (15
October), it most likely failed due to a website configuration problem
(file execute permissions). That problem has been fixed.
Bob Stayton
Sagehill E
Adding xi:fallback elements to the source would work for that:
http://www.w3.org/TR/xinclude/#fallback_element
David
> -Original Message-
> From: Schramm, Martin [mailto:[EMAIL PROTECTED]
> Sent: Monday, October 15, 2007 8:32 AM
> To: docbook-apps@lists.oasis-open.org
> Subject: [docboo
Quoting "Schramm, Martin" <[EMAIL PROTECTED]>:
But sometimes there is no data to be published in those files. So there
is no file and the specific folder is empty, where the xinclude
reference points to. In this case, when we publish the "mother" file as
HTML or FO/PDF, there is naturally an err
Your wiki engine may already have html2wiki scripts. If so, you could
convert the docbook to html and then convert that to wiki markup. You
could customize tweak docbook2html xsls and/or the html2wiki scripts as
needed to improve the results. I'm sure you'll have to do something
special to deal wit
Dear list,
I like to ask you for support in the following case:
We have a DB "mother" document, which contains lots of xinclude
references to other files. Many of these referenced files are generated
by scripts (containing tables with test results). These generated files
are written in valid DocB
Hi,
I'm thinking of putting together some DocBook -> Wiki XSL
stylesheets. This is to attempt to solve the problemm (other
suggestions gratefully received) of handling simultaneous multiple
reviewers of a DocBook document.
The idea is that, having put together the Admin Guide for a relea
13 matches
Mail list logo
