atom feed10 messages in org.oasis-open.lists.docbook-appsRe: [docbook-apps] unresolved xinclud...
FromSent OnAttachments
Bob StaytonOct 28, 2003 7:20 pm 
Daniel VeillardOct 29, 2003 2:09 am 
Bob StaytonOct 29, 2003 9:32 am 
Daniel VeillardOct 29, 2003 2:35 pm 
Bob StaytonOct 29, 2003 4:23 pm 
Daniel VeillardOct 30, 2003 2:51 pm 
David PrattOct 31, 2003 9:32 am 
Bob StaytonOct 31, 2003 11:15 am 
Daniel VeillardNov 4, 2003 3:20 pm 
Bob StaytonNov 4, 2003 4:31 pm 
Subject:Re: [docbook-apps] unresolved xincludes with xsltproc
From:Bob Stayton (bo@sco.com)
Date:Oct 29, 2003 4:23:41 pm
List:org.oasis-open.lists.docbook-apps

On Wed, Oct 29, 2003 at 05:38:58PM -0500, Daniel Veillard wrote:

On Wed, Oct 29, 2003 at 08:49:36AM -0800, Bob Stayton wrote:

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.

yes, but xmllint doesn't generate this error if run on the fragment you pasted. There is something weird going on.

Should I file a bug report?

yes but provide the full set of informations so I can try to reproduce it.

Done.

I also filed two other bug reports. One was for the original problem of a bad xpointer in an xinclude href not producing an error message (still true in version 2.6.1), and one for extraneous validation errors when using --postvalid with xincludes.