Modify

Opened 10 years ago

Closed 10 years ago

#1321 closed Bugs (fixed)

invalid docbook in tool documentation

Reported by: Frank Mori Hess Owned by: Vladimir Prus
Milestone: To Be Determined Component: build
Version: Boost Development Trunk Severity: Problem
Keywords: Cc:

Description

The current boost.build docs don't work with apache fop 0.94 when building boost.pdf. The attached patch changes the top-level element of the build documentation from a <part> to a <chapter>, since boost.xml includes the build documentation inside a <part> already (<part> is not permitted to have another <part> as child). This also requires various <chapter> and <appendix> elements to be changed into <section>s.

The standalone doc is modified to reparent the top-level <section>s back into <chapter> and <appendix> elements, so it's output should be unchanged.

Attachments (0)

Change History (8)

comment:1 Changed 10 years ago by Frank Mori Hess

Hmm, trac won't let me attach my patch, it thinks the xml is spam:

Submission rejected as potential spam (Maximum number of external links per post exceeded, Akismet says content is spam)

comment:2 Changed 10 years ago by Vladimir Prus

Please talk to Boost moderators as to why attachment does not work.

Also: if the patch touches anything in build system? From your description it sounds like not, in which case it's not my bug.

comment:3 Changed 10 years ago by Frank Mori Hess

Here are links to the patch anyways:

first version (the build_docs.patch attachment):

http://article.gmane.org/gmane.comp.lib.boost.documentation/3206

second version of patch to standalone.xml:

http://article.gmane.org/gmane.comp.lib.boost.documentation/3210

comment:4 Changed 10 years ago by Frank Mori Hess

FYI, I've worked around this issue by extending the hack in docbook.xsl for dealing with nested <part> elements. So, apache fop is okay makeing the build docs without my earlier patches. The patch to docbook.xsl is here:

http://article.gmane.org/gmane.comp.lib.boost.documentation/3222

and will probably be applied to the trunk next week.

comment:5 Changed 10 years ago by Daniel James

I'm trying to clean up the documentation related tickets. Should this one be resolved as fixed?

comment:6 Changed 10 years ago by anonymous

No idea :-)

comment:7 Changed 10 years ago by Frank Mori Hess

Yes, I think so.

comment:8 Changed 10 years ago by Daniel James

Resolution: fixed
Status: newclosed

Modify Ticket

Change Properties
Set your email in Preferences
Action
as closed The owner will remain Vladimir Prus.
The resolution will be deleted.

Add Comment


E-mail address and name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.