This is the mail archive of the
docbook-apps@lists.oasis-open.org
mailing list .
Re: Re: Using fo-patch-for-fop.xsl and question aboutXHTML namespaces
- From: Daniel Veillard <veillard at redhat dot com>
- To: Carlos Araya <carlos at cvc dot edu>
- Cc: docbook-apps at lists dot oasis-open dot org
- Date: Wed, 09 Jan 2002 09:29:29 -0500
- Subject: Re: DOCBOOK-APPS: Re: Using fo-patch-for-fop.xsl and question aboutXHTML namespaces
- References: <878zb77jh4.fsf@nwalsh.com> <B861922E.2977%carlos@cvc.edu>
- Reply-to: veillard at redhat dot com
On Wed, Jan 09, 2002 at 06:22:38AM -0800, Carlos Araya wrote:
> On 01/09/02 5:16, "Norman Walsh" <ndw@nwalsh.com> wrote:
>
> > / Carlos Araya <carlos@cvc.edu> was heard to say:
> > | I have two more questions after which I believe I can go back to writing.
> > |
> > | Is there a way to eliminate the xmlns: declarations from every single
> > | element on an XHTML file? They are hardcoded into each page and I don't know
> >
> > What processor are you using? It isn't wrong to have them on every
> > element, but it also isn't necessary. Saxon, for example, only outputs
> > one at the top.
> I am using XSLTProc. I don't have a problem with leaving the namespace on
> every element, it's just that it's extra text being downloaded that doesn't
> need to be IMO.
Strange ... I'm pretty sure I check for inherited namespaces on created
nodes before generating any new namespace.
> > Urk. Sorry. After you've produced x.fo using the regular stylesheets,
> > process it with fo-patch-for-fop.xsl to produce x.fop and pass that to
> > FOP. It's just another stylesheet.
> Thanks, it works
There is something which I don't understand.
If you think there is a bug please fill one if possible with the inputs
to the processor.
Daniel
--
Daniel Veillard | Red Hat Network https://rhn.redhat.com/
veillard@redhat.com | libxml Gnome XML XSLT toolkit http://xmlsoft.org/
http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/