I suspect the bug's actually in your css. Try it without your css and
see if the problem goes away.
David
> -----Original Message-----
> From: Johnson, Eric [mailto:]
> Sent: Friday, November 30, 2007 3:12 PM
> To: David Cramer
> Cc: docbook-apps
> Subject: RE: [docbook-apps] Weird characters in generated HTML
>
> I found the problem...
>
> It seams that the java processors generate <a id="foo" /> for
> anchors and xsltproc generates <a id="foo"></a>. Firefox and
> IE7 don't like <a id="foo" />. I'm pretty sure the guy who
> originally did our customization layer didn't change the
> olink stuff, but I could be wrong.
> Where would I look to figure out how to make the Java XSLT
> processors do the right thing?
>
>
>
> -----Original Message-----
> From: David Cramer [mailto:]
> Sent: Friday, November 30, 2007 3:01 PM
> To: Johnson, Eric
> Cc: docbook-apps
> Subject: RE: [docbook-apps] Weird characters in generated HTML
>
> Check for an empty <a href=""/> element immediately before
> the "everything's a link" stuff starts. Then trace back to
> your docbook source (or your customization layer) to find
> where the emtpy <a href=""/> is coming from.
>
> David
>
> > -----Original Message-----
> > From: Eric Johnson [mailto:]
> > Sent: Friday, November 30, 2007 1:30 PM
> > To: David Cramer
> > Cc: docbook-apps
> > Subject: RE: [docbook-apps] Weird characters in generated HTML
> >
> > Thnaks, I should have seen that. That fixed the hatted A's, but I
> > still cannot figure out why all my content is being
> rendered as links.
> > I haven't changed the source that I used when working with xsltproc.
> >
> > On Fri, 2007-11-30 at 11:14 -0600, David Cramer wrote:
> > > Take a look at
> http://www.sagehill.net/docbookxsl/SpecialChars.html
> > > (scroll down to "Odd characters in HTML output").
> > >
> > > David
> > >
> > > > -----Original Message-----
> > > > From: Eric Johnson [mailto:]
> > > > Sent: Friday, November 30, 2007 11:04 AM
> > > > To: docbook-apps
> > > > Subject: [docbook-apps] Weird characters in generated HTML
> > > >
> > > > Sorry for the stream of newby questions...
> > > >
> > > > I got both Saxon and Xalan to work with XIncludes and
> > catalogs from
> > > > Ant.
> > > > However, all of my generated HTML, using either
> > processor, comes out
> > > > as a link....
> > > > Using Xalan I also got a bunch of hatted A's (an A wearing a
> > > > ^) where ever there is a hard space.
> > > > Using Saxon my target database file for olinks has a
> > space at the top.
> > > > Using xsltproc under Windows, with the same source and
> > customization
> > > > layer, this never happened.
> > > > Any ideas?
> > > >
> > > >
> > --------------------------------------------------------------------
> > > > - To unsubscribe, e-mail:
> > > >
> > > > For additional commands, e-mail:
> > > >
> > > >
> > > >
> >
>
