headers
Adder | 19 Jul 23:00

function.xml vs boostbook.dtd

Hi,

It seems that the attribute xmlns:xi="http://www.w3.org/2001/XInclude"
on the "library" element is not supported by boostbook.dtd.

All the files that use <xi:include href="..."> generate errors when
processed with xsltproc ("Using libxml 20632, libxslt 10123 and
libexslt 813").

The MSXML parser signals the same error (function.xml, line 6).

I would like to ask someone who is more experienced with BoostBook to
take 5 minutes of his/her time and test the instructions posted here
http://www.boost.org/doc/libs/1_35_0/doc/html/boostbook/getting/started.html
on Windows (only up to building function.xml, even without downloading
local copies of the DTD/XSD files.

They don't seem to work... unless skipping validation against the
boostbook.dtd file (e.g. by erasing the file).

Thank you,

--

-- 
Best regards,
 Adder
Permalink | Reply |
headers
Daniel James | 20 Jul 21:07

Re: function.xml vs boostbook.dtd

2008/7/19 Adder <adder.thief <at> gmail.com>:
>
> It seems that the attribute xmlns:xi="http://www.w3.org/2001/XInclude"
> on the "library" element is not supported by boostbook.dtd.
>
> All the files that use <xi:include href="..."> generate errors when
> processed with xsltproc ("Using libxml 20632, libxslt 10123 and
> libexslt 813").

It seems that most boostbook documents aren't valid according the the
dtd, which isn't a good situation but doesn't generally cause
problems. Xsltproc normally only requires well formed documents.

> The MSXML parser signals the same error (function.xml, line 6).
>
> I would like to ask someone who is more experienced with BoostBook to
> take 5 minutes of his/her time and test the instructions posted here
> http://www.boost.org/doc/libs/1_35_0/doc/html/boostbook/getting/started.html
> on Windows (only up to building function.xml, even without downloading
> local copies of the DTD/XSD files.
>
> They don't seem to work... unless skipping validation against the
> boostbook.dtd file (e.g. by erasing the file).

I'm afraid I'm not much help, as I don't use windows. You might find
the quickbook installation instructions helpful:

http://www.boost.org/tools/quickbook/doc/html/quickbook/install/windows.html

You mentioned in your earlier email that you tried the metacomm
(Continue reading)

Permalink | Reply |
headers
Adder | 22 Jul 17:05

Re: function.xml vs boostbook.dtd

Sunday, July 20, 2008, 10:07:34 PM, Daniel James wrote:

DJ> 2008/7/19 Adder <adder.thief <at> gmail.com>:
>>
>> It seems that the attribute xmlns:xi="http://www.w3.org/2001/XInclude"
>> on the "library" element is not supported by boostbook.dtd.
>>
>> All the files that use <xi:include href="..."> generate errors when
>> processed with xsltproc ("Using libxml 20632, libxslt 10123 and
>> libexslt 813").

DJ> It seems that most boostbook documents aren't valid according the the
DJ> dtd, which isn't a good situation but doesn't generally cause
DJ> problems. Xsltproc normally only requires well formed documents.

After un-commenting lines 27-36 of boostbook.dtd, xsltproc
successfully processes files that contain xi:include !

We still get the error:

  function.xml:6: namespace error : Namespace prefix xmlns for xi on library is not defined
    xmlns:xi="http://www.w3.org/2001/XInclude">

but xsltproc can proceed, despite this message. Could it be that the
element "library" does not support the "xmlns:xi" attribute ?

>> The MSXML parser signals the same error (function.xml, line 6).
>>
>> I would like to ask someone who is more experienced with BoostBook to
>> take 5 minutes of his/her time and test the instructions posted here
(Continue reading)

Permalink | Reply |
headers
Daniel James | 22 Jul 17:23

Re: function.xml vs boostbook.dtd

2008/7/22 Adder <adder.thief <at> gmail.com>:
>
> After un-commenting lines 27-36 of boostbook.dtd, xsltproc
> successfully processes files that contain xi:include !

You can build the documentation now?

> We still get the error:
>
>  function.xml:6: namespace error : Namespace prefix xmlns for xi on library is not defined
>    xmlns:xi="http://www.w3.org/2001/XInclude">
>
> but xsltproc can proceed, despite this message. Could it be that the
> element "library" does not support the "xmlns:xi" attribute ?

>From the comment, it looks like Douglas Gregor didn't find the time to
work it out. I don't know if anyone here really understand DTDs. Maybe
we should look into the more recent schema languages, which are meant
to be simpler.

You could probably suppress the error with the '--novalid' flag.
Actually, I wonder if you've previously configured an XML tool to be
'strict'? Maybe an environment variable or something like that?

> Sorry for having "spammed" the list a little bit. :(

There's nothing to apologise for. You didn't get a reply the first time.

> I have unpacked the two xsltproc versions in separate folders; none of
> them is in the PATH. I have xsltproc.bat in the path, redirecting to
(Continue reading)

Permalink | Reply |
headers
Adder | 23 Jul 00:13

Re: function.xml vs boostbook.dtd

>> After un-commenting lines 27-36 of boostbook.dtd, xsltproc
>> successfully processes files that contain xi:include !

DJ> You can build the documentation now?

With those modifications to boostbook.dtd, I've got over the errors
I've mentioned. Indeed, I can build documentation for "function" and
other libraries that use <xi:include href="..." />.

If there are no problems with these modifications on other platforms,
I would humbly suggest they are committed.

Unfortunately, I am now stuck at a later point. As I didn't get any
pictures or links to other libs when building from
"trunk/libs/function/doc", I have moved to "trunk/doc" and run "bjam"
from that folder.

After 10 minutes of work, I got several repetitions of these error
messages ("cerr output"):

    runtime error: file file://...trunk/tools/boostbook/xsl/doxygen/doxygen2boostbook.xsl line 226
element element
    Variable 'actual-class-key' has not been declared.
    xmlXPathCompiledEval: evaluation failed
    runtime error: file file://...trunk/tools/boostbook/xsl/doxygen/doxygen2boostbook.xsl line 226
element element
    xsl:element: The attribute 'name' is missing.

The "cout output" was:
(Continue reading)

Permalink | Reply |

Gmane