The DAPS forum on Sourceforge is now closed, please use GitHub

Stefan Knorr — Tue, 11 Feb 2020 19:34:52 -0000

Hello,

Frank, Thomas, and I who are maintaining DAPS have decided that we should try to unify the web presence of DAPS as much as possible. This forum was the last part of DAPS still hosted on Sourceforge instead of GitHub. It too shall now go and be replaced by GitHub. Unfortunately, GitHub does not have forum functionality, but given the volume of this forum, it should be just fine to replace it with the GitHub issue tracker.

There is now a new "forum" label on GitHub, please use it for discussion posts.

The following URL shows an overview of all posts with that label so far (currently none): https://github.com/openSUSE/daps/issues?q=is%3Aissue+label%3Aforum
This link will open a new topic: https://github.com/openSUSE/daps/issues/new?labels=forum (You will need a GitHub account to open a new topic.)

Both links are also featured in the navigation bar of the DAPS homepage.

All discussions here are now set to be read-only.

A final goodbye to Sourceforge, you've been good. :)

Adding profiling variables

Frank Sundermeyer — Mon, 04 Mar 2019 12:09:51 -0000

DAPS supports all profiling variables that upstream DocBook supports. These are

XML: arch, DC-file: PROFARCH
XML: audience, DC-file: PROFAUDIENCE
XML: condition, DC-file: PROFCONDITION
XML: conformance, DC-file: PROFCONFORMANCE
XML: lang, DC-file: PROFLANG
XML: os, DC-file: PROFOS
XML: outputformat, DC-file: PROFOUTPUTFORMAT
XML: revision, DC-file: PROFREVISION
XML: revisionflag="added|changed|deleted|off, DC-file: PROFREVISIONFLAG
XML: role, DC-file: PROFROLE
XML: security, DC-file: PROFSECURITY
XML: status, DC-file: PROFSTATUS
XML: userlevel, DC-file: PROFUSERLEVEL
XML: vendor, DC-file: PROFVENDOR
XML: wordsize, DC-file: PROFWORDSIZE

All but revisionflag can be used with arbitrary strings, so they are not bound to a certain usecase. Therefore the list above should be sufficient for almost all usecases (if not, your docs will become difficult to maintain anyway ;-D).
With the SUSE documentation, we use arch in its intended sense (to differentiate between architectures), but os to distinguish between different product flavors.

For detailed information on how to use profiling with DAPS, refer to the DAPS documentation:

Profiling—Support for Document Variants https://opensuse.github.io/daps/doc/cha.daps.user.modular.html#sec.daps.user.modular.profile
Combining Entities and Profiling https://opensuse.github.io/daps/doc/cha.daps.user.modular.html#sec.daps.user.modular.productentities

NOTE: To profile for more than one value for a single profiling attribute, you need to separate the values in the DC-file by semicolon:

PROFARCH="i586;i686,x86_64"
PROFOS="basic;professional"
PROFVENDOR="MyCompany"

Adding profiling variables

Bob Stafford — Fri, 01 Mar 2019 18:17:05 -0000

For my project just using the condition variable for profiling is not enough I need to use multiple profiling variables.

I've been trying to add these additional profiling parameters to the processing but it's truning out to be more complicated than I'd hoped, I've had to change the rng file, the stylesheets, and even the daps script but I've still not got it working.
Is there a simpler way to add new profiling variables to the ones initially provided by DAPS?

Info element not allowed and expected

Bob Stafford — Wed, 13 Feb 2019 01:42:39 -0000

That fixed it. Many thanks!!

Info element not allowed and expected

Thomas Schraitle — Tue, 12 Feb 2019 13:19:55 -0000

Hi Bob,

thanks for your message! Your eec-bookinfo.xml contains two issues:

You use the DOCTYPE declaration of the DTD.
Your info element does not include the DocBook 5 namespace.

That's why you get validation errors, because an info element in no namespace is not allowed in DocBook 5.

I would propose to change your code in eec-bookinfo.xml like this:

<!DOCTYPE info [
     <!ENTITY % xinclude SYSTEM "eec-xinclude.mod">
     <!ENTITY % edge-defs SYSTEM "eec-edge-defs.mod">
     %xinclude;
     %edge-defs;
]> -->

 <!-- +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
   Here is book information that may be used in certain stylesheets like PDF and HTML -->
<info xml:id="eec-bookinfo" xmlns="http://docbook.org/ns/docbook">
 <!--<title>&EDGE; Manual</title>-->
 <title>EDGE Manual</title>
 <!-- ... --> 
</info>

Hope this helps. :-)

Best,
Tom

Info element not allowed and expected

Bob Stafford — Sun, 10 Feb 2019 23:08:39 -0000

Further progress of sorts, by running the bigfile mode on my source I get this, whoch shows that the include has added two attributes to the info block, if I add those attributes to the info block directly in my book I get the same strange error about info not being allowed.

So it seems include is adding attributes (xmlns="" xml:base="eec-bookinfo.xml") that upset the validator.

<?xml version="1.0"?>
<?xml-model href="http://docbook.org/xml/5.0/rng/docbookxi.rng"
            schematypens="http://relaxng.org/ns/structure/1.0"?><book xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:xi="http://www.w3.org/2001/XInclude" xmlns="http://docbook.org/ns/docbook" xml:base="MAIN-EDGE-API.xml" xml:id="book.edge.api" xml:lang="en" version="5.0">
 <info xmlns="" xml:base="eec-bookinfo.xml">
 <title>EDGE Manual</title>
 </info>

 <chapter>
 <title>Introduction</title>
 </chapter>

</book>

Info element not allowed and expected

Bob Stafford — Sun, 10 Feb 2019 22:44:55 -0000

The problem seems to be related to including the info block, if I put the info block directly in the book block it works

<?xml version="1.0" encoding="UTF-8"?>
<?xml-model href="http://docbook.org/xml/5.0/rng/docbookxi.rng"
            schematypens="http://relaxng.org/ns/structure/1.0"?>

<book xml:id="book.edge.api" xml:lang="en" version="5.0"
      xmlns:xlink="http://www.w3.org/1999/xlink"
      xmlns:xi="http://www.w3.org/2001/XInclude"
      xmlns="http://docbook.org/ns/docbook">

 <info>
 <title>EDGE Manual</title>
 </info>

 <chapter>
 <title>Introduction</title>
 </chapter>

</book>

If I replace the info block with an include and put the same info block in the included file I get the error message from my first post.

<?xml version="1.0" encoding="UTF-8"?>
<?xml-model href="http://docbook.org/xml/5.0/rng/docbookxi.rng"
            schematypens="http://relaxng.org/ns/structure/1.0"?>

<book xml:id="book.edge.api" xml:lang="en" version="5.0"
      xmlns:xlink="http://www.w3.org/1999/xlink"
      xmlns:xi="http://www.w3.org/2001/XInclude"
      xmlns="http://docbook.org/ns/docbook">
 <xi:include href="eec-bookinfo.xml"/>

 <chapter>
 <title>Introduction</title>
 </chapter>
</book>

where eec-bookinfo.xml contains

<?xml version="1.0" encoding="UTF-8"?>
 <info>
 <title>EDGE Manual</title>
 </info>

Any suggestions much appreciated.

Info element not allowed and expected

Bob Stafford — Sun, 10 Feb 2019 17:15:26 -0000

I'm converting a docbook project to use daps and I'm getting messages like this one which seem to be saying that info is not allowed despite info being in the list of expected elements. Any suggestions are welcome.

/home/bobstaff/pulse/doc/api/docbook/build/.profiled/noprofile/eec-bookinfo.xml:12:53: error: element "info" not allowed here; expected the element end-tag or element "acknowledgements", "appendix", "article", "bibliography", "chapter", "colophon", "dedication", "glossary", "index", "info", "part", "preface", "reference", "titleabbrev", "toc", "topic" or "xi:include"

I have this xml/docbook source

<book xml:id="book.edge.api" xml:lang="en" version="5.0"
      xmlns:xlink="http://www.w3.org/1999/xlink"
      xmlns:xi="http://www.w3.org/2001/XInclude"
      xmlns="http://docbook.org/ns/docbook">
 <title>EDGE API Documentation</title>
 <subtitle>EDGE API Documentation</subtitle>
 <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="eec-bookinfo.xml"/>

eec-bookinfo.xml starts with

<?xml version="1.0" encoding="UTF-8"?>
<!--
<!DOCTYPE info PUBLIC "-//OASIS//DTD DocBook XML V5.0//EN"
     "http://www.docbook.org/xml/5.0/docbookx.dtd" [
     <!ENTITY % xinclude SYSTEM "eec-xinclude.mod">
     <!ENTITY % edge-defs SYSTEM "eec-edge-defs.mod">
     %xinclude;
     %edge-defs;
]> -->

 <!-- +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
   Here is book information that may be used in certain stylesheets like PDF and HTML -->
<info id="eec-bookinfo">
 <!--<title>&EDGE; Manual</title>-->
 <title>EDGE Manual</title>

DAPS 3.0.0 Release

Hamish McIntyre-Bhatty — Fri, 18 Jan 2019 16:35:22 -0000

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

DAPS 3.0.0 Release

Frank Sundermeyer — Fri, 18 Jan 2019 16:10:14 -0000

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

Recent posts to Discussion, old (read-only)

The DAPS forum on Sourceforge is now closed, please use GitHub

Adding profiling variables

Adding profiling variables

Info element not allowed and expected

Info element not allowed and expected

Info element not allowed and expected

Info element not allowed and expected

Info element not allowed and expected

DAPS 3.0.0 Release

DAPS 3.0.0 Release