Hi Graeme,
Use the <merge> element instead of <info> in structure or module for merged
content like title. The DocBook TC decided that using info for merged
elements had the effect of overloading info's semantics. Normally info in
DocBook contains metadata about its parent element, so that a revhistory in
structure/info can describe the revisions in the assembly file. We added
<merge> to contain content to be merged with the resources being pulled in.
Currently any elements contained in info in an assembly is not included in
the assembled document, as you discovered.
BTW, title is no longer valid as a child of structure. See Norm's
documentation at:
http://docbook.org/tdg51/en/html/structure.html
So the bug here is that title worked. 8^)
Bob Stayton
Sagehill Enterprises
[email protected]
--------------------------------------------------
From: <[email protected]>
Sent: Friday, June 07, 2013 8:08 AM
To: <[email protected]>
Subject: Re: [docbook-apps] DocBook assembly generation: missing top-level
titles
Hi Robert,
Thanks for your reply. That certainly works as you suggest:
<?xml version="1.0"?>
<article xmlns="http://docbook.org/ns/docbook"; version="5.0"
xml:id="mcw-data-storage-guide"><title>Article
Title</title><section><section version="5.0"><info>
<title xmlns:xlink="http://www.w3.org/1999/xlink";
xmlns:xi="http://www.w3.org/2001/XInclude";
xmlns:svg="http://www.w3.org/2000/svg";
xmlns:mml="http://www.w3.org/1998/Math/MathML";
xmlns:html="http://www.w3.org/1999/xhtml";
xmlns:db="http://docbook.org/ns/docbook";>Thing1</title>
However, I'm not clear on why it should be necessary to do it that way.
The DocBook guide provides examples where the <title> element is inside
a <book><info> hierarchy. Plus, it's inconsistent with other title
elements (e.g. the module-level title in my original example).
Thanks,
Graeme
On Fri, Jun 7, 2013, at 12:34, Robert Fekete wrote:
Hi,
have you tried putting the title outside the <info> tag?
Like:
<structure xml:id="guide">
<output renderas="article"/>
<title>My Article Title</title>
<module renderas="section">
I use it that way with the same toolchain and it works for me.
Robert
On 06/07/2013 10:41 AM, [email protected] wrote:
> Hi there,
> I'm using version 1.78.1 of the DocBook stylesheets to generate
> articles
> from DocBook assembly. Which is nice! But here's my problem: top-level
> element titles are missing from the output.
>
> Given this structure, the output is lacking its top-level element title
> (in this case, the article title):
>
> <?xml version="1.0"?>
> <assembly xmlns:xlink="http://www.w3.org/1999/xlink";
> xmlns="http://docbook.org/ns/docbook";>
> <resources xml:base="topics/reference">
> ...
> </resources>
> <structure xml:id="guide">
> <output renderas="article"/>
> <info>
> <title>My Article Title</title>
> </info>
> <module renderas="section">
> <info>
> <title>My Section</title>
> </info>
> <module resourceref="guide-articles"/>
> <module resourceref="guide--lists"/>
> </module>
> <module resourceref="guide-thing1"/>
> <module resourceref="guide-thing2"/>
> <module resourceref="guide-thing3"/>
> </structure>
> </assembly>
>
> Here's the snipped output of assemble.xsl:
>
> <?xml version="1.0"?>
> <article xmlns="http://docbook.org/ns/docbook"; version="5.0"
> xml:id="guide">
> <section>
> <section version="5.0">
> <info>
> <title
> xmlns:xlink="http://www.w3.org/1999/xlink";
> xmlns:xi="http://www.w3.org/2001/XInclude";
> xmlns:svg="http://www.w3.org/2000/svg";
> xmlns:mml="http://www.w3.org/1998/Math/MathML";
> xmlns:html="http://www.w3.org/1999/xhtml";
> xmlns:db="http://docbook.org/ns/docbook";>Thing
> 1</title>
> </info>
> <para>The text of thing1</para>
>
>
> I don't quite understand how it could miss out this detail.
>
> I'm using xsltproc to run the stylesheet transformation.
>
> Any help would be appreciated.
>
> Thanks,
>
> Graeme
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
