HI Graeme,
Well, this appears to be a bug in assemble.xsl. The merge process works
when the structure element has a resourceref attribute like module, but not
when it defines the root element of the output. I'll fix that.
As a workaround, you can create a file with an empty article element, create
a resource element that points to that file, and reference that resource
with a resourceref attribute on the structure element. Then the merge will
work.
Bob Stayton
Sagehill Enterprises
b...@sagehill.net
--------------------------------------------------
From: <gra...@heliocentrik.net>
Sent: Wednesday, June 12, 2013 1:55 AM
To: "Bob Stayton" <b...@sagehill.net>; <docbook-apps@lists.oasis-open.org>
Subject: Re: [docbook-apps] DocBook assembly generation: missing top-level
titles
Hi Bob,
Thanks for that
I'm finding that when I use the '<merge>' element for this purpose, only
the 'title' element of the metadata gets copied into the final output.
Things like 'revhistory' and 'edition' are missing. With a structure
like this:
<structure xml:id="myarticle">
<output renderas="article"/>
<merge>
<publisher><publishername>My Name</publishername></publisher>
<pubdate>2013-02-07</pubdate>
<title>Document Title</title>
<revhistory>
<revision>
<revnumber>1.0</revnumber>
<date>24 Sept 2012</date>
<revremark>A draft.</revremark>
</revision>
</revhistory>
<edition>Version 1.0</edition>
<biblioid otherclass="Tracking number">00484844</biblioid>
</merge>
<module resourceref="section"/>
</structure>
I get output like this:
<article>
<title>Document Title</title>
<info/>
<section>
</section>
</article>
Is there a way of having these elements show up in my consolidated
document?
Thanks,
Graeme
On Fri, Jun 7, 2013, at 17:15, Bob Stayton wrote:
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
b...@sagehill.net
--------------------------------------------------
From: <gra...@heliocentrik.net>
Sent: Friday, June 07, 2013 8:08 AM
To: <docbook-apps@lists.oasis-open.org>
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, gra...@heliocentrik.net 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:
>> > docbook-apps-unsubscr...@lists.oasis-open.org
>> > For additional commands, e-mail:
>> > docbook-apps-h...@lists.oasis-open.org
>> >
>> >
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org
>> For additional commands, e-mail:
>> docbook-apps-h...@lists.oasis-open.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org
> For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org
For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org