Lillian,
Regarding question #2, my team ran into this same problem last week and found 
it only occurred in Firefox 3.x (not in Firefox 2.x and not in IE-we didn't 
check other browsers). Part of the problem is that Firefox 3.x expects *valid* 
XHTML (while earlier versions didn't). And, I guess the XHTML output from 
DocBook (using Saxon 6.5.5, at least) is not valid XHTML with respect to 
closing anchor tags. Our quick fix was to switch to outputting HTML instead of 
XHTML. A co-worker who investigated this problem says there's an add-on for 
Saxon that makes it generate XHTML, but I don't know much beyond that.

HTH!
cheri


From: Lillian Sullam [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 01, 2008 2:59 PM
To: [email protected]
Subject: [docbook-apps] <link linkend> in XHTML output

Hello,

This is a two part question.

1. When I create chunked XHTML my <link linkend> tags do not seem to translate 
to XHTML. The ID are missing, and the links don't work. Is there a way to solve 
this without changing the way I link items in DocBook?

2. In every part of my chunked document the text reacts to any "hovering" of 
the mouse.  This should not happen, not all of the text is a link.

Here is a sample of the output XHTML code:





<div class="sect1" lang="en">





         <div class="titlepage">

            <div>

               <div>





                  <h2 class="title" style="clear: both">





                     <a id="Title 1"/>Title 1</h2>





               </div>

            </div>

         </div>

         <p>Some text here.</p> 1





         <p>Some more text. A link <a class="link" href="Link_to_name">Link 
Name</a> 2 even more text.</p> 3





         <div class="sect2" lang="en">





            <div class="titlepage">

               <div>

                  <div>





                     <h3 class="title">

                        <a id="d0e726"/>Title 2</h3> 4






1 Text reacts to "hover"
2 Text reacts to "hover"
3 Text no longer reacts to "hover"
4 Text reacts to "hover"

I have a feeling this has to do with the <a> tag being closed with a "/" 
instead of </a>, but why is this happening?

Lillian

Reply via email to