I think it's a fair question for the docbook-apps list. He's getting different behavior from the docbook xslts using different processors and using the xslt processor he was told is the preferred one (saxon), he's getting obiviously bad output (everything's a hyperlink). Other lists wouldn't know enough about how we put all the tools together. The xslt list would probably tell him there's no difference between <a id="foo"/> and <a id="foo"></a>. I think he's actually got a poorly written css rule.
David > -----Original Message----- > From: Dave Pawson [mailto:[EMAIL PROTECTED] > Sent: Saturday, December 01, 2007 2:19 AM > To: Johnson, Eric > Cc: docbook-apps > Subject: Re: [docbook-apps] Weird characters in generated HTML > > Johnson, Eric wrote: > > As far as I can tell it is all of the anchors. Not just the > olink ones. > > I'm calling Saxon, with Xerces, from ant using the java task: > > > > Since your questions focus on ant, java and xslt, why are you > asking them on the docbook mailing lists? > > Try the ant list, the xslt list etc. > > > regards > > -- > Dave Pawson > XSLT XSL-FO FAQ. > http://www.dpawson.co.uk > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: > [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
