In 2012 an issue regarding validation of DocBook 5 had been resolved, but with current DAPS 2 (trunk rev. 4350) it was actually not possible for me to validate any DocBook 5 XML source.
It turned out that the validate.mk passes a variable DOCBOOK5_RNG_URI to the validator (jing), which is nowhere defined.
I could work around this by just adding
This is true. However, if you log into SF it should be possible. We configured the project to allow everyone who is logged in to file bug reports. This makes it a bit easier to ask questions and the user get notified whenever something has changed. This would be not possible for anonymous users.
As for the other points: Yes, validation is currently investigated and Frank changed some things lately. I've created ticket [#247] for you if you want to watch its progress.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
does not work on my openSUSE because it calls /usr/bin/saxon which does not exist.
Workaround:
cd /usr/bin; ln -s saxon6 saxon
This is dangerous. Don't do that.
At the moment, we have saxon6 and saxon9 as packages. DAPS needs saxon6, not saxon9. The latter handles XSLT 2.0 and cannot be used with XSLT 1.0 stylesheets due to extension functions. These extension functions are only provided for saxon6.
Have you installed the package saxon6? This provides the above link and you have the appropriate JAR files.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
sorry for not having replied earlier - I exchanged the keyboard with a paintbrush for a few days ;-).
It turned out that the validate.mk passes a variable DOCBOOK5_RNG_URI to the validator (jing), which is nowhere defined.
It is defined in /etc/daps/config (and can be customized in ~/.daps/config). However, this is just the URN to the schema. It gets resolved via xmlcatalog in daps/bin and the path is written to DOCBOOK5_RNG.
Using DOCBOOK5_RNG_URI rather than DOCBOOK5_RNG in validate.mk caused the error. This has been fixed in r4374 in trunk/.
Thanks for bringing up this issue
Also the daps XSLT wrapper script under /usr/share/daps/libexec/daps-xslt
does not work on my openSUSE because it calls /usr/bin/saxon which does not exist.
Thomas answer to this issue was not 100% correct. In openSUSE, the link is provided by the package saxon6-scripts. It needs to be installed manually--the saxon6 does not pull it in automatically.
Hope this helps, Frank
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
In 2012 an issue regarding validation of DocBook 5 had been resolved, but with current DAPS 2 (trunk rev. 4350) it was actually not possible for me to validate any DocBook 5 XML source.
It turned out that the validate.mk passes a variable DOCBOOK5_RNG_URI to the validator (jing), which is nowhere defined.
I could work around this by just adding
at the top of validate.mk.
Also the daps XSLT wrapper script under
does not work on my openSUSE because it calls /usr/bin/saxon which does not exist.
Workaround:
I would like to file bugs for these issues, but don't know how: https://sourceforge.net/p/daps/tickets/ lacks a "Create Ticket" button.
Hi Stefan,
thanks for starting this discussion! :)
Let's start with the simple things:
This is true. However, if you log into SF it should be possible. We configured the project to allow everyone who is logged in to file bug reports. This makes it a bit easier to ask questions and the user get notified whenever something has changed. This would be not possible for anonymous users.
As for the other points: Yes, validation is currently investigated and Frank changed some things lately. I've created ticket [#247] for you if you want to watch its progress.
This is dangerous. Don't do that.
At the moment, we have
saxon6
andsaxon9
as packages. DAPS needssaxon6
, notsaxon9
. The latter handles XSLT 2.0 and cannot be used with XSLT 1.0 stylesheets due to extension functions. These extension functions are only provided forsaxon6
.Have you installed the package saxon6? This provides the above link and you have the appropriate JAR files.
Hi Stefan,
sorry for not having replied earlier - I exchanged the keyboard with a paintbrush for a few days ;-).
It is defined in /etc/daps/config (and can be customized in ~/.daps/config). However, this is just the URN to the schema. It gets resolved via xmlcatalog in daps/bin and the path is written to DOCBOOK5_RNG.
Using DOCBOOK5_RNG_URI rather than DOCBOOK5_RNG in validate.mk caused the error. This has been fixed in r4374 in trunk/.
Thanks for bringing up this issue
Thomas answer to this issue was not 100% correct. In openSUSE, the link is provided by the package saxon6-scripts. It needs to be installed manually--the saxon6 does not pull it in automatically.
Hope this helps, Frank