openSUSE / daps

DocBook Authoring and Publishing Suite (DAPS)
https://openSUSE.github.io/daps
Other
62 stars 18 forks source link

[ADOC] Generating `online-docs` fails with DTD error #499

Closed r0ckarong closed 5 years ago

r0ckarong commented 5 years ago

Problem description

I'm trying to publish the first CaaSP v4 doc with DAPS and AsciiDoc. I can generate the outputs fine on their own on my machine. When I try to generate online-docs it fails with a DTD error.

File: https://github.com/SUSE/doc-caasp/blob/adoc/adoc/quick-deployment.adoc

DC-File: https://github.com/SUSE/doc-caasp/blob/adoc/DC-caasp-quickstart

~I noticed this was happening because I added the adoc branch to the susedoc.github.io config but no content shows up. I can not find out how to check on Travis if something fails or why (I don't even know where to log in or find the build responsible for this task, the HHG is sorely unhelpful about this).~

Is this something wrong with my input file? ~Is this something broken on travis or with the build config?~

Expected behavior

The docs build and get published as expected.

Steps to reproduce the behavior

Attempt to generate online docs from above file using DAPS 3.0.

r0ckarong commented 5 years ago

The publishing was a different problem, the DTD error persists with online-docs parameter.

ghost commented 5 years ago

Hm, unfortunately, the Novdoc DTD expects data that we don't have :(

[...]doc-caasp/build/caasp-quickstart/online-docs/set_en_bigfile.xml:3: element bookinfo:
  validity error : Element bookinfo content does not follow the DTD, expecting (title ,
  productname+ , productnumber?, date? , releaseinfo? , titleabbrev? , legalnotice+ ,
  authorgroup* , abstract*), got (title date legalnotice authorgroup)

You're lacking a productname here and I don't know of a way to supply that in AsciiDoc (at least with asciidoctor-compatible AsciiDoc; with asciidoc you could supply a -docinfo.xml file but that is not supported in asciidoctor).

fsundermeyer commented 5 years ago

Contrary to the comment above, asciidoctor also supports the -docinfo.xml files. Providing such a file with the missing elements will solve the isue.