Hi Camille,
@2008-02-11 16:02 +0100:
after crawling up about a dozen templates I found out why my orgname was
not showing on verso book titlepage. It was not referenced within
person.name.first-last so I modified the template (see below). I'm not
sure this is the right place nor the right
Hi Alan,
This customization pretty much does what you want. It turns out I didn't have
to change the book template, only the way the chapters were handled. I copied
match=chapter template from fo/component.xsl, and changed the match on it to
only match on the first chapter in a sequence:
Bob,
Many thanks!
In the meantime I also managed to get your other suggested approach to
work - making the document an article instead of a book. Originally when
I did this fop produced the error
page-sequence must be child of root, not fo:flow
It occurred to me today that if I
Oh, and the template is looking for para elements, not section
elements...
You would be better off leaving the template as is and adding the role
attribute to the para element, that is
para role=scopechange the color/para
Alan
-Original Message-
From: 61Sniper [mailto:[EMAIL PROTECTED]
The advantage of matching text()[ancestor::*/@role = 'scope']|xref[
ancestor::*/@role = 'scope' ] is that you can then add role=scope to
any element and all the text within that element will be affected. So
you would do this in your customization layer:
xsl:template match=text()[
Hallo,
thank you for the replies. I have changed the following lines
section status=scope
para
change the color
/para
/section
xsl:template match=[EMAIL PROTECTED] = 'scope']
fo:block xsl:use-attribute-sets=normal.para.spacing
David is right. Role is usually a better attribute for this. I believe
Bob's most excellent book (http://www.sagehill.net/docbookxsl/)
discusses this.
Here is a snippet from a customization layer I'm using. It customizes
the fo translation. The xsl:import should point to the location of your
The section attribute should be named role, not status...
Alan
-Original Message-
From: 61Sniper [mailto:[EMAIL PROTECTED]
Sent: Tuesday, February 12, 2008 1:09 PM
To: docbook-apps@lists.oasis-open.org
Subject: Re: [docbook-apps] change the color of a paragrapfh
Hallo,
thank you for
-Original Message-
From: spr
However, I still get the sequence as:
- Chapter Title
- Chapter ToC
- Chapter Abstract
After many failed attempts, i tried to format the abstract
such that i can
visually separate it from ToC with this customization:
See this message:
http://www.oasis-open.org/archives/docbook-apps/200801/msg00152.html
For this technique to work, you should add the template to a
customization layer
http://www.sagehill.net/docbookxsl/CustomMethods.html#CustomizationLaye
r.
Btw., do you really want to do it based on id? I
Hello all,
how can I change the color of the following paragraph
para id=testpara
Change my color
/para
I have tried with
xsl:attribute-set id=testpara
xsl:attribute name=colorbluexsl:attribute
/xsl:attribute-set
It doesn`t work.
--
View this message in context:
See the thread I started on 17/12/2007, Headed Fop unable to render
tables ? (without intervention ?).
The outcome is that you need to put a processing instruction
?dbfo keep-together=auto ?
In your FO.
And I think you need to use the latest snapshot version of the xsl
stylesheets from
I've been trying to get a book to have no page breaks before chapters in
the PDF output. Bob Stayton offered the advice that a chapter element
generates a page-sequence in FO output, and a page sequence always
starts on a new page. If you want to use book and chapter, you'll need
to customize
13 matches
Mail list logo
