10 messages in org.oasis-open.lists.docbook-appsRe: [docbook-apps] unresolved xinclud...| From | Sent On | Attachments |
|---|---|---|
| Bob Stayton | Oct 28, 2003 7:20 pm | |
| Daniel Veillard | Oct 29, 2003 2:09 am | |
| Bob Stayton | Oct 29, 2003 9:32 am | |
| Daniel Veillard | Oct 29, 2003 2:35 pm | |
| Bob Stayton | Oct 29, 2003 4:23 pm | |
| Daniel Veillard | Oct 30, 2003 2:51 pm | |
| David Pratt | Oct 31, 2003 9:32 am | |
| Bob Stayton | Oct 31, 2003 11:15 am | |
| Daniel Veillard | Nov 4, 2003 3:20 pm | |
| Bob Stayton | Nov 4, 2003 4:31 pm |
| Subject: | Re: [docbook-apps] unresolved xincludes with xsltproc | |
|---|---|---|
| From: | Bob Stayton (bo...@sco.com) | |
| Date: | Oct 29, 2003 9:32:09 am | |
| List: | org.oasis-open.lists.docbook-apps | |
On Wed, Oct 29, 2003 at 05:12:55AM -0500, Daniel Veillard wrote:
On Tue, Oct 28, 2003 at 06:38:13PM -0800, Bob Stayton wrote:
I notice when using XIncludes with xsltproc that it will report an error when it cannot open the file referenced by the href attribute. But if you use the xpointer syntax, there is no error if the file is there but the xpointer does not resolve.
For example, a bad filename:
<xi:include href="badname.xml#foo"/>
will fail with this message:
warning: failed to load external entity "badname.xml" XInclude: could not load badname.xml#foo, and no fallback was found
But when I use a good filename but a bad id in the xpointer, I get no error message at all:
<xi:include href="goodname.xml#nosuchid"/>
Neither xmllint nor xsltproc report this as a problem. Nor does it use the fallback, if it is specified. But of course, this is a problem if content goes missing because of a typo in the xpointer expression.
I realize that an xpath expression that resolves to no nodes is a valid expression, but it is not what was intented. Does anyone have a way to flag such missing XIncludes?
Hum, sounds like a sub-resource error, did you tried with libxml2-2.6.x ? IF you still see the problem, please bugzilla it: http://xmlsoft.org/bugs.html
I just downloaded and compiled libxml2-2.6.1 and libxslt-1.0.33 on my Linux box. This version seems to be having namespace problems. Now when I process any docbook file with the DocBook XSL stylesheets I get lots of these errors:
------------------------------------------------------------------- ../docbook-xsl-1.62.4/common/af.xml:2: namespace error : Namespace prefix xmlns for l on l10n is not defined .sourceforge.net/xmlns/l10n/1.0" language="af" english-language-name="Afrikaans" ^ ../docbook-xsl-1.62.4/common/af.xml:2: namespace error : Namespace prefix l on l10n is not defined .sourceforge.net/xmlns/l10n/1.0" language="af" english-language-name="Afrikaans" ^ ../docbook-xsl-1.62.4/common/af.xml:10: namespace error : Namespace prefix l on gentext is not defined <l:gentext key="Abstract" text="Samevatting"/> ^ etc.
------------------------------------------------------------------- These errors are repeated for all the other locale files.
But the first file in question (common/af.xml) starts like this:
<?xml version="1.0" encoding="US-ASCII"?> <l:l10n xmlns:l="http://docbook.sourceforge.net/xmlns/l10n/1.0" language="af" english-language-name="Afrikaans">
It sure looks to me like the "l" namespace is defined.
Should I file a bug report?
--
Bob Stayton 400 Encinal Street Publications Architect Santa Cruz, CA 95060 Technical Publications voice: (831) 427-7796 The SCO Group fax: (831) 429-1887 email: bo...@sco.com