Re: [docbook-apps] unresolved xincludes with xsltproc

[Bob Stayton <bobs@sco.com>]

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.

-- 

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: bobs@sco.com