Bob,
I'm not sure if I'd recognize whether the two differences I note below are
causing functional differences as I'm very new to titlepage customization. I
shall report back if I do think I've found anything.
I got my first bit of title-page customization working, though more by
guesswork than from the docs.
On recognizing font-family as an fo:block attribute I tried adding break-after
as an attribute.
ie changing :
<t:titlepage t:element="article" t:wrapper="fo:block"
font-family="{$title.fontset}" >
to :
<t:titlepage t:element="article" t:wrapper="fo:block"
font-family="{$title.fontset}" break-after="page" >
And that worked. Ie I got a page-break after the title.
Then I found something that told me that was what I needed to do - Note 5 in
Example 11.1.
I'm not yet sure why it worked - there are some pages somwehere on the
titlepage configuration elements, but I can't now find them.
I'll want to add some element positioning and coloured blocks, lines and images.
Eventually,
Richard.
[Blue line]
Richard Kerry
BNCS Engineer
T: +44 (0)20 82259063
M: +44 (0)7812 325518
Room EBX 301, BBC Television Centre, Wood Lane, London, W12 7RJ
[email protected]<https://webmail.siemens-it-solutions.com/owa/redir.aspx?C=9fb20d019e3e4cb99344d708709a3177&URL=mailto%3arichard.kerry%40atos.net>
uk.atos.net<https://webmail.siemens-it-solutions.com/owa/redir.aspx?C=9fb20d019e3e4cb99344d708709a3177&URL=http%3a%2f%2fuk.atos.net%2fen-uk%2f>
[Atos logo]
This e-mail and the documents attached are confidential and intended solely for
the addressee; it may also be privileged. If you receive this e-mail in error,
please notify the sender immediately and destroy it. As its integrity cannot be
secured on the Internet, the Atos group liability cannot be triggered for the
message content. Although the sender endeavours to maintain a computer
virus-free network, the sender does not warrant that this transmission is
virus-free and will not be liable for any damages resulting from any virus
transmitted.
________________________________
From: Bob Stayton [[email protected]]
Sent: 24 November 2012 00:44
To: Kerry, Richard; [email protected]
Subject: Re: [docbook-apps] RE: Title-page customization - is it just me ?
Hi Richard,
Thanks for pointing out these inconsistencies. I think I know why they are
happening, and I'll correct them for the next release.
I hope they are not producing any functional differences. If so, please point
them out.
Bob Stayton
Sagehill Enterprises
[email protected]<mailto:[email protected]>
From: Kerry, Richard<mailto:[email protected]>
Sent: Friday, November 23, 2012 9:58 AM
To: DocBook Apps Mailing List
[[email protected]]<mailto:[email protected]]�>
Subject: [docbook-apps] RE: Title-page customization - is it just me ?
Well - no sooner do I send my question than I make some progress, and realize
it was me ....
(checking a query I sent to the list back in July)
Since I'm using Docbook 5 I need to use the ns stylesheets.
Having done that I get the processed file being nearly the same as the
published one.
The xml header PI differs in that mine states encoding="utf-8" which the
published one doesn't.
The xsl:stylesheet lists the namespaces in different orders.
And the "This stylesheet was cretated" comment is slightly different.
Both the above differences I think are trivial, though i'm surprised the
generated one is not the same as the published one as regards the comment. I
think the namespace name differences are just due to the processor.
Further down the file I find the following in my generated file, but absent
from the published one.
<xsl:when test="d:docinfo/d:title">
<xsl:apply-templates mode="topic.titlepage.recto.auto.mode"
select="d:docinfo/d:title"/>
</xsl:when>
and
<xsl:when test="d:docinfo/d:subtitle">
<xsl:apply-templates mode="topic.titlepage.recto.auto.mode"
select="d:docinfo/d:subtitle"/>
</xsl:when>
I am suprised at this difference as I'd expect the real content in the
published files to correspond to the source as published.
Now I do need to work out what to do to get the page-break added.
And then the removal of the Rev History from the beginning and moving it to the
end and adding another.
Progressively,
Richard.
Richard Kerry
BNCS Engineer
T: +44 (0)20 82259063
M: +44 (0)7812 325518
Room EBX 301, BBC Television Centre, Wood Lane, London, W12 7RJ
[email protected]<https://webmail.siemens-it-solutions.com/owa/redir.aspx?C=9fb20d019e3e4cb99344d708709a3177&URL=mailto%3arichard.kerry%40atos.net>
uk.atos.net<https://webmail.siemens-it-solutions.com/owa/redir.aspx?C=9fb20d019e3e4cb99344d708709a3177&URL=http%3a%2f%2fuk.atos.net%2fen-uk%2f>
This e-mail and the documents attached are confidential and intended solely for
the addressee; it may also be privileged. If you receive this e-mail in error,
please notify the sender immediately and destroy it. As its integrity cannot be
secured on the Internet, the Atos group liability cannot be triggered for the
message content. Although the sender endeavours to maintain a computer
virus-free network, the sender does not warrant that this transmission is
virus-free and will not be liable for any damages resulting from any virus
transmitted.
________________________________
From: Kerry, Richard [[email protected]]
Sent: 23 November 2012 17:09
To: DocBook Apps Mailing List [[email protected]]
Subject: [docbook-apps] Title-page customization - is it just me ?
I'm sure it is me, but I can't seem to get this to work.....
I want to customize my (PDF via FO) document.
I want to make the title-page a separate page, ie to insert a page-break. My
document is an <article>.
I'm using docbook-xsl-1.77.1 stylesheets, and Docbook 5.
Following the instructions in Bob's book I've taken a copy of
fo\titlepage.templates.xml.
I process it using template\titlepage.xsl and Saxon 6-5-5. I call the result
mytitlepages.xsl.
If I then compare my mytitlepages.xsl with the supplied
fo\titlepage.templates.xml I find that all the elements which are <fo:block> in
the given file are <block> in my generated one.
For example :
published: <fo:block xmlns:fo="http://www.w3.org/1999/XSL/Format";
font-family="{$title.fontset}">
against
generated: <block font-family="{$title.fontset}">
If I then <import> my generated file I get streams of error messages - the
first of which is :
Error at fo:block on line 342 of
file:/C:/Users/Richard/Downloads/DocBook/docbook-xsl-1.77.1/fo/refentry.xsl:
No attribute-set exists named refnamediv.titlepage.recto.style
and the others are similar.
I am assuming these are being caused by this inconsistency in the xsl.
Can anyone advise what I might be doing wrong ?
I am assuming that as the published stylesheets have been around for a while
they are right ....
And that Bob's book is accurate.
Note that at this stage my local titlepage.templates.xml is unmodified, yet is
showing this inconsistency. I would expect processing the published
titlepage.templates.xml would generate a copy of the published
titlepage.templates.xsl.
Once I've got this aspect sorted my next task will be to work out exactly what
I need to put where to get a page-break after the article recto title page.
Puzzledly,
Richard.
PS,
Once I've got the title page on a separate page I'll want to move the revision
history somewhere else, ie to near the end of the document.
Actually I want it at the end, since it would be before the Index, but there
isn't an Index.
And then I'm going to want two separate Revision Histories, one for the
document and one for the software to which it refers.
Richard Kerry
BNCS Engineer
T: +44 (0)20 82259063
M: +44 (0)7812 325518
Room EBX 301, BBC Television Centre, Wood Lane, London, W12 7RJ
[email protected]<https://webmail.siemens-it-solutions.com/owa/redir.aspx?C=9fb20d019e3e4cb99344d708709a3177&URL=mailto%3arichard.kerry%40atos.net>
uk.atos.net<https://webmail.siemens-it-solutions.com/owa/redir.aspx?C=9fb20d019e3e4cb99344d708709a3177&URL=http%3a%2f%2fuk.atos.net%2fen-uk%2f>
This e-mail and the documents attached are confidential and intended solely for
the addressee; it may also be privileged. If you receive this e-mail in error,
please notify the sender immediately and destroy it. As its integrity cannot be
secured on the Internet, the Atos group liability cannot be triggered for the
message content. Although the sender endeavours to maintain a computer
virus-free network, the sender does not warrant that this transmission is
virus-free and will not be liable for any damages resulting from any virus
transmitted.
________________________________
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
blank
Description: blank
--------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
