Bug 915687 - Metadata-pulling abstract.xsl script does not work for DocBook 5
Summary: Metadata-pulling abstract.xsl script does not work for DocBook 5
Keywords:
Status: CLOSED DUPLICATE of bug 1005042
Alias: None
Product: Publican
Classification: Community
Component: publican
Version: 3.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jeff Fearn 🐞
QA Contact: tools-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-02-26 10:37 UTC by Fintan Bolton
Modified: 2016-08-16 01:27 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-09-23 06:33:49 UTC
Embargoed:


Attachments (Terms of Use)
Version of abstract.xsl script that works also in DocBook 5 (553 bytes, text/xml)
2013-02-26 10:37 UTC, Fintan Bolton
no flags Details

Description Fintan Bolton 2013-02-26 10:37:41 UTC
Created attachment 702763 [details]
Version of abstract.xsl script that works also in DocBook 5

Description of problem:

The current version of the publican/datadir/xsl/abstract.xsl script (which is used to extract the abstract text from a book) does not work in DocBook 5. Attached is a modified version of the abstract.xsl file, which should work for both DocBook 4 and DocBook 5


Version-Release number of selected component (if applicable): Tested in publican 3.0

Comment 1 Jeff Fearn 🐞 2013-02-26 22:36:13 UTC
FYI the DB5 support is very early and completely broken. We really should not have included it in Publican 3.0, calling it a tech preview is extremely generous to the code quality.

On the flip side it has made it very clear that splicing DocBook5 support in to the DocBook4 code is un-maintainable in the mid to long term.

In the long run setting up the code for proper sub-packaging will allow us much greater opportunity for supporting multiple input formats and make getting DB4 and DB5 support working in harmony much less of a struggle.

Comment 2 Jeff Fearn 🐞 2013-09-23 06:33:49 UTC

*** This bug has been marked as a duplicate of bug 1005042 ***


Note You need to log in before you can comment on or make changes to this bug.