Re: [docbook-apps] Code problems

["Bob Stayton" <bobs@sagehill.net>]

Hi,
I checked your first abstract example, the one you said you tried on
Windows, and it is not valid. It has empty para elements inside the address
element.  How did you check the validation?

I tried your second example (which did validate) in Xalan 2.6.0 on Windows
XP with the stock docbook-xsl-1.68.1, and the HTML it produced did have an
active link on the ulinks.  So I don't see where the problem is yet.
Looking at the ulink template, it always outputs an <a> element in HTML.

Also, it is often useful to test with another processor such as Saxon 6.5.3.

Bob Stayton
Sagehill Enterprises
DocBook Consulting
bobs@sagehill.net


----- Original Message ----- 
From: "SIRIGINA Saraswathi" <SSirigina@COVANSYS.COM>
To: <docbook-apps@lists.oasis-open.org>
Sent: Wednesday, April 06, 2005 11:06 PM
Subject: [docbook-apps] Code problems


Hi -

Just wanted to share this with the list and see if anyone encountered
the same and if so, the correct way they handled this:


I have ulinks in my address. And I am trying to generate XML to HTML on
a WINDOWS XP box with XALAN processor and on a Linux box with the XMLTO
util.

I am using Docbook XSL Stylesheets 1.68.1 and the Docbook DTD 4.4

The code on Windows XP with XALAN does not generate a hyperlink to the
ulink in the generated HTML if included in an <otheraddr>. My XML passes
validation. However, the same code on Linux requires an <otheraddr> tag
to generate the hyperlink as well as to validate the XML.

I have used a customization layer.

Here is my XML code on Windows:

 <abstract>
  <para>
                    <informaltable frame="none">
                    <tgroup cols="2">
                    <colspec colname="c1" colwidth="13px"/>
                    <colspec colname="c2" colwidth="15px"/>
                    <tbody>
                    <row>
                    <entry align="left" valign="top">
                    <para>
                    <address>
                        <para/>
                        GT.M Group
                        Fidelity Information Services, Inc.
                        <street>2 West Liberty Boulevard, Suite
300</street>
                        <city>Malvern, </city><state>PA
</state><postcode> 19355, </postcode>
                        <country>United States of America</country>
                     </address>
                        </para>
                        </entry>
                        <entry align="right" valign="top">
                        <para>
                        <address>
                        <para/>
                        <phone>GT.M Support: +1 (610) 578-4226</phone>
                        <phone>Switchboard: +1 (610) 296-8877 </phone>
                        <fax>Fax: +1 (484) 595-5101 </fax>
                        <ulink
url="http://www.sanchez-gtm.com";>http://www.sanchez-gtm.com</ulink>
                        <ulink
url="mailto:gtmsupport@fnf.com";>gtmsupport@fnf.com</ulink>
                    </address>
                    </para>
                    </entry>
                    </row>
                    </tbody>
                    </tgroup>
                    </informaltable>
  </para>
                </abstract>

************************************************************
On LINUX:

 <abstract>
  <para>
                    <informaltable frame="none">
                    <tgroup cols="2">
                    <colspec colname="c1" colwidth="13px"/>
                    <colspec colname="c2" colwidth="15px"/>
                    <tbody>
                    <row>
                    <entry align="left" valign="top">
                    <para>
                    <address>

                        GT.M Group
                        Fidelity Information Services, Inc.
                        <street>2 West Liberty Boulevard, Suite
300</street>
                        <city>Malvern, </city><state>PA
</state><postcode> 19355, </postcode>
                        <country>United States of America</country>
                     </address>
                        </para>
                        </entry>
                        <entry align="right" valign="top">
                        <para>
                        <address>

                        <phone>GT.M Support: +1 (610) 578-4226</phone>
                        <phone>Switchboard: +1 (610) 296-8877 </phone>
                        <fax>Fax: +1 (484) 595-5101 </fax>
                        <otheraddr><ulink
url="http://www.sanchez-gtm.com";>http://www.sanchez-gtm.com</ulink></oth
eraddr>
                        <otheraddr><ulink
url="mailto:gtmsupport@fnf.com";>gtmsupport@fnf.com</ulink> </otheraddr>
                    </address>
                    </para>
                    </entry>
                    </row>
                    </tbody>
                    </tgroup>
                    </informaltable>
  </para>
                </abstract>

****************************************************

To suppress the Abstract title from displaying here is my customization:

<!-- abstracts without titles -->
<xsl:template match="abstract" mode="title.markup">
<xsl:param name="allow-anchors" select="1"/>

 </xsl:template>


***********************************************************
Here is some additional code I commented out:

<!-- display link target url after link name -->
<!-- (in print, only display name would appear) -->
<!-- suppresses target if target and name are identical -->
<!-- applies to: fo output only -->
<!-- 0: display url name only, suppress url target -->
<!-- 1: display url name and url target in brackets -->
<!--<xsl:param name="ulink.show">1</xsl:param>-->

***********************************************************



Please suggest as to what is wrong with my code.

Thanks,
Sarah
Confidentiality Statement:

This message is intended only for the individual or entity to which it is
addressed. It may contain privileged, confidential information which is
exempt from disclosure under applicable laws. If you are not the intended
recipient, please note that you are strictly prohibited from disseminating
or distributing this information (other than to the intended recipient) or
copying this information. If you have received this communication in error,
please notify us immediately by return email.