Menu

DAPS 3.0.0 Release

2018-11-09
2019-01-18
  • Frank Sundermeyer

    Hi,

    almost 1 ½ years after DAPS 2.4 it is time for a new major release: DAPS 3.0.

    With this release we are proud to announce a significant addition to the DAPS feature set: AsciiDoc support. In addition to creating your documens from DocBook, you can now also create them from AsciiDoc sources. And it does not stop here: you will be able to use your existing DocBook stylesheets with your AsciiDoc sources!

    Want to know more details? See the AsciiDoc Quickstart (which, of course, was generated from AsciiDoc sources, using the same stylesheets as for the rest of the DAPS documentation, which is still DocBook-based).

    Eighteen months is a long time and so there are more features/changes/bugfixes that went into the new release. here is the Changelog:

    New Features

    • added support for ASCIIDOC sources
    • added support for LibreOffice Draw images (*.odg)
    • added support for specifying a config file on the command line
      (with --config)
    • added SVG support for HTML builds
    • integrated hunspell and make aspell optional
    • initial well-formedness check ignores duplicated IDs (this
      allows to have identical IDs in parts that get profiled)
    • initial well-formedness warns about missing xi:include files
    • daps-autobuild now supports building single books (via the
      --dcfiles option)
    • DAPS prgram name and version are passed to stylesheets with
      xslt parameters converter.name and converter.version
    • implement file not found for XIncludes
    • FOP and XEP version numbers are shown in debug/verbose output
    • various improvements for the DocBook to NovDoc conversion
    • split lib/daps_functions into several files to improve speed
      and maintainability

    Bugfixes

    • 476: DAPS generates ODG->SVG files into images/src
    • 475: Tab completion creates error
    • 474: Potentially wrong variable assignment
    • 437: lodraw tries to convert empty SVG
    • 469: RPMLINT complains about permissions of XSLT stylesheet
    • 468: xmlwellformed script creates RPMLINT warning
    • 466: Build issues with daps-xmlwellformed
    • 464: xmlformat incorrectly formats variablelist terms
    • 462: Implement file not found for XIncludes
    • 459: By default, use the xep-daps.xml configuration from
      stylesheets
    • 457: Ship the asciidoc postprocessing stylesheet
    • 455: Transform glosslist into variablelist (NovDoc conversion)
    • 453: Cleanup stylesheet for results from ASCIIDoctor
    • 452: Make it possible to specify the ASCIIDOC doc type
    • 439: Make xmlformat more verbose in debug mode
    • 435: require java-devel >= 1.8.0
    • 425: Well-formedness check fails with double occurrences
      of xml:ids
    • 424: Fix XML catalog generation
    • 422: Integrate hunspell and make aspell optional
    • 421: Show FOP and XEP version in debug/verbose output
    • 419: HTML and PDF builds need different paths for Admonition
      and Callout Images
    • 416: DAPS Won't Built With UTF-8 Characters in XML Filenames
    • 415: Add support for LibreOffice Draw files
    • 397: Spaces in path problem
    • 322: Add documentation for --xmlonly / --imgonly switches
      for the list-srcfiles subcommand
    • 226: Let stylesheets know which version of DAPS calls them
    • 119: daps-init: also include example for set
    • show a warning when an existing PDF has a size of 0 bytes
      (usually the result of a failed FOP build)
    • PDF fails when static links in build/.tmp already exist
    • fixed DocBook identifiers in configure.ac
    • made unpack-lopcdrop more robust against non-critical issues;
      improved its debugging output

    Documentation

    • new guide: ASCIIDOC Quick Start
    • Various updates to reflect changes in the code
    • Improve help text for daps-xslt
    • Improve error message for IDs defined multiple times

    Removed support for:

    • sourcing DC-files
    • help texts for deprecated daps 1.x commands

    Misc

    • converted Python scripts to Python 3; changed build
      dependencies to python3
     
  • Hamish McIntyre-Bhatty

    This looks great, but unfortunately I can't compile this. When I try, this is the output I get:

    make[1]: Entering directory '.../daps-3.0.0'
    touch build/.firstbuild
    make[2]: Entering directory '.../daps-3.0.0'
    make[2]: Leaving directory '.../daps-3.0.0'
    make[2]: Entering directory '.../daps-3.0.0'
    .../daps-3.0.0/doc/build/.profiled/noprofile/daps-asciidoc.xml:213:144: error: element "emphasis" not allowed here; expected the element end-tag, text or element "alt", "anchor", "annotation", "biblioref", "indexterm", "inlinemediaobject", "link", "olink", "phrase", "remark", "replaceable", "subscript", "superscript" or "xref"
    .../daps-3.0.0/doc/build/.profiled/noprofile/daps-asciidoc.xml:240:84: error: element "emphasis" not allowed here; expected the element end-tag, text or element "alt", "anchor", "annotation", "biblioref", "indexterm", "inlinemediaobject", "link", "olink", "phrase", "remark", "replaceable", "subscript", "superscript" or "xref"
    .../daps-3.0.0/make/validate.mk:40: recipe for target '.../daps-3.0.0/doc/build/.profiled/noprofile/.validate' failed
    make[2]: *** [.../daps-3.0.0/doc/build/.profiled/noprofile/.validate] Error 1
    make[2]: Leaving directory '.../daps-3.0.0'
    Makefile:1858: recipe for target 'doc/build/daps-asciidoc/single-html/daps-asciidoc/daps-asciidoc.html' failed
    make[1]: *** [doc/build/daps-asciidoc/single-html/daps-asciidoc/daps-asciidoc.html] Error 1
    make[1]: Leaving directory '.../daps-3.0.0'
    Makefile:1265: recipe for target 'all-recursive' failed
    make: *** [all-recursive] Error 1
    

    I'm guessing I'm missing a build dependency or something? I'm running Linux Mint 19.1, based on Ubuntu 18.04. Also, how do I enable docbook 5.1 support - whatever I do it doesn't seem to enable it?

    Thanks,
    Hamish

     
  • Frank Sundermeyer

    Do you have asciidoctor or asciidoc as a build requirement? Looks like it builds the asciidoc documentation and fails to generate valid XML. I assume that this is caused by asciidoc. Can you try asciidoctor instead and see if it works?

    If not, try to remove asciidoc/asciidoctor from the build dependencies. In that case the asciidoc document will not be built and the error should go away (the resulting DAPS will, nevertheless support ASCIIDoc).
    Looks like I should work on https://github.com/openSUSE/daps/issues/486

    What do you mean with docbook 5.1 support is not enabled? Does configure report this during build or are you not able to process DocBook 5.1 documents with a compiled DAPS?

     
  • Hamish McIntyre-Bhatty

    Thanks for quick reply. I have asciidoctor installed, but not asciidoc. It works now I've removed it - thanks :)

    Yeah, when I run the configure script, I get this:

    DocBook 5.1 support              |    no   | install DocBook 5.1, the
                                     |         | DocBook 5 XSL stylesheets,
                                     |         | and jing
    

    jing is installed, so I'm assuming one of the others isn't, or it's not being detected that they are. I don't know how to install them though. It's always said this, so not new, but I have a different issue that I think might be related to this, so I want to fix it now.

     

    Last edit: Hamish McIntyre-Bhatty 2019-01-17
  • Thomas Schraitle

    I'm running Linux Mint 19.1, based on Ubuntu 18.04. Also, how do I enable docbook 5.1 support - whatever I do it doesn't seem to enable it?

    I'm not very familiar with Ubunut or Linux Mint. For Ubuntu, however, I've found there is the docbook5-xml package. Try to install that the configure script will find the DocBook schema.

    Hope that will help. :-)

     
  • Thomas Schraitle

    I forgot to mention, check also if you have installed the docbook-xsl-ns and docbook-xsl packages.

     
  • Hamish McIntyre-Bhatty

    Fair enough :)

    Nope, still not working. A package search doesn't yield any docbook 5.1 - specific things, so I think there probably just isn't a package for the docbook 5.1 stuff. Thanks anyway :)

     
  • Frank Sundermeyer

    The lack of DocBook 5(.1) is most likely also the reason why building the AsciiDoc manual fails during compilation. AsciiDoctor produces a DB 5 XML file from the AsciiDoc sources that gets validated afterwards. And that validation step fails in the example you posted above.

    I have created an issue for this: https://github.com/openSUSE/daps/issues/488

     
  • Hamish McIntyre-Bhatty

    Good idea. I know docbook 5.0 works, because that's what I used to write my documentation that I process with DAPS.

     

Anonymous
Anonymous

Add attachments
Cancel





Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.