You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you use a document written in GeekoDoc/DocBook 5 which contains XPointers with the xpointer() scheme, the process gives you this error message:
build/.profiled/x86_64_zseries_power_aarch64_article/art_pcidss.xml:11:114: warning:
SchemeUnsupported: The XPointer scheme 'xpointer' is not supported.
As Jing depends on Xerces and Xerces does not support the XPointer xpointer() scheme, Jing fails.
Expected behavior
The XPointer is resolved correctly.
At the moment, I only see the option to use xmllint to resolve any XInclude/XPointer and validate afterwards with jing.
Steps to reproduce the behavior
In the SLE repository:
Open the file art_pcidss.xml in your editor.
Inside the DOCTYPE declaration, add the following additional line:
Jing fails as it depends on Xerces. As Xerces does not support
the xpointer() scheme, we need to give jing a "complete"
document. The document is created by `xmllint`.
Currently it's an ugly implementation as it appends ".resolved"
to the `PROFILED_MAIN` variable. Probably we need to adapt the
code in other locations too.
For the time being, it's just the validate subcommand.
Problem description
If you use a document written in GeekoDoc/DocBook 5 which contains XPointers with the
xpointer()
scheme, the process gives you this error message:As Jing depends on Xerces and Xerces does not support the XPointer
xpointer()
scheme, Jing fails.Expected behavior
The XPointer is resolved correctly.
At the moment, I only see the option to use
xmllint
to resolve any XInclude/XPointer and validate afterwards withjing
.Steps to reproduce the behavior
In the SLE repository:
Open the file
art_pcidss.xml
in your editor.Inside the DOCTYPE declaration, add the following additional line:
Replace the following line:
with this line:
Validate with
daps
to get the error above:The text was updated successfully, but these errors were encountered: