Menu

#590 Missing and empty href in <a> from <ulink>

output: HTML
closed-invalid
XSL (1066)
5
2005-02-01
2004-12-10
No

Using the the none-chunked docboox.xsl to transform into XHTML, a

<ulink url="http://sourceforge.net/">link</ulink>

yields

<a ="" target="_top">link</a>

Use the included build.xml to transform test.xml into test.html. The included test.html has already been reformated to simplify review of this bug.

In order to find the docbook-xsl stuff, make sure that it is a located in xml/docbook-xsl/xhtml/docbook.xsl, or modify the related

<xslt ... style="xml/docbook-xsl/xhtml/docbook.xsl">

in the build.html.

Ant should generated the following output:

----------
Buildfile: build.xml

init:

bug-missing-href:
[xmlvalidate] 1 file(s) have been successfully validated.
[xmlvalidate] .../test.html:12:63: Attribute "xmlns" must be declared for element type "div".
[xmlvalidate] .../test.html:19:67: Attribute "xmlns" must be declared for element type "div".
[xmlvalidate] .../test.html:34:67: Attribute "xmlns" must be declared for element type "div".
[xmlvalidate] .../test.html:40:57: Attribute "xmlns" must be declared for element type "p".
[xmlvalidate] .../test.html:41:24: Element type "a" must be followed by either attribute specifications, ">" or "/>".

BUILD FAILED
.../build.xml:23: Could not validate document .../test.html
----------

The "Attribute xmlns must be declared" messages are already covered by [bug 1061942] (Spurious xmlns="" with Xerces/Xalan), but this one exposes the problem of my bug:

Element type "a" must be followed by either attribute specifications, ">" or "/>".

I'm using ant 1.6.1 from the fink distribution under MacOS 10.3.5.

Discussion

  • Thomas Aglassinger

    contains build.xml and test.xml to reproduce bug

     
  • Martin Stemplinger

    Logged In: YES
    user_id=150711

    Same behaviour under Windows XP with ant 1.6.2

     
  • Robert Stayton

    Robert Stayton - 2005-02-01

    Logged In: YES
    user_id=193218

    I can confirm this behavior, but only with the Xalan 2.5.1
    processor. It works correctly in xsltproc, Saxon 6.5.3, and
    Xalan-J 2.6.0. I've looked at the code, and I don't see
    anything wrong with the XSL template. So I conclude it must
    be a bug in Xalan 2.5.1.

     
  • Robert Stayton

    Robert Stayton - 2005-02-01
    • assigned_to: nobody --> bobstayton
    • status: open --> closed-invalid