Re: [Refdb-users] xhtml references don't start on new line

[David N. <dav...@bi...>]

Hi Markus,

>I'm afraid this may be a display problem of your browser. The output
>looks just fine over here (Firebird 0.7 on FreeBSD).
>

Updating to latest CVS version had no effect, as I suspected.

I have, however, noted another rendering bug: the actual references do 
not appear as hyperlinks in Firebird or Firefox.

The offending xhtml fragment is:
........................................................................................................................
... quotes, such as <a xmlns="" href="#IDSavitch2001">(Savitch, 
2001)</a> and <a xmlns="" href="#IDLamport1994">(Lamport, 1994)</a>, for 
it to work ...
........................................................................................................................

The problem is the empty xmlns attributes.  If I manually remove them, 
both browsers display the hyperlinks.  If the namespace attribute is a 
legal part of the xhtml specification, then this is another problem with 
Firebird/Firefox and xhtml.

Almost as an afterthought, at this point I ran the original xhtml file 
through the W3C validator <http://validator.w3.org/>.  It returned the 
following information:
........................................................................................................................
This page is not Valid XHTML 1.0 Transitional!

Below are the results of attempting to parse this document with an SGML 
parser.

   1. Line 5, column 1002: there is no attribute "xmlns" (explain...).

  ...o make some quotes, such as <a xmlns="" 
href="#IDSavitch2001">(Savitch, 2001)
                                          ^

   2. Line 5, column 2413: there is no attribute "xmlns" (explain...).

  ...ry.  So, here goes ?</p></div><div xmlns="" id="id2502984" 
class="bibliogra
                                          ^

   3. Line 5, column 2547: ID "id2502984" already defined (explain...).

  ...lepage"><div><div><h2 class="title"><a id="id2502984"></a>Reference 
List</h2>
                                          ^

   4. Line 5, column 2420: ID "id2502984" first defined here (explain...).

  ..., here goes ?</p></div><div xmlns="" id="id2502984" 
class="bibliography"><d
                                          ^

   5. Line 5, column 2656: document type does not allow element "div" 
here; missing one of "object", "applet", "map", "iframe", "button", 
"ins", "del" start-tag

  ...<div id="IDLamport1994" class="bibliomixed">Lamport L., 1994, 
LaTeX: A Docume
                                          ^

   6. Line 5, column 2800: document type does not allow element "div" 
here; missing one of "object", "applet", "map", "iframe", "button", 
"ins", "del" start-tag

  ...<div id="IDSavitch2001" class="bibliomixed">Savitch W., 2001, Java. 
An Introd
                                          ^

   7. Line 5, column 2957: document type does not allow element "div" 
here; missing one of "object", "applet", "map", "iframe", "button", 
"ins", "del" start-tag

  ...><p><div id="id2563143" 
class="bibliomixed"></div></p></div></div></body></ht
                                          ^
........................................................................................................................

I note that this result is from an SGML parser and W3C list some 
limitations of that parser, but none of them seem to apply here.  The 
W3C validator is complaining about the parts of the document that render 
poorly on my Firefox and Firebird:
 - Errors 1 and 2 ("no attribute xmlns")
     -> the citations involved don't render as hyperlinks.
 - Errors 5-7 ("document type does not allow element 'div' here")
     -> these are the references, which don't start on their own line.

I had a look at the XHTML standard as parsed by dtdparse (see 
<http://dtdparse.sourceforge.net/xhtml10/>) and found that:
- the <a> element has no 'xmlns' attribute.  Perhaps this is a wandering 
namespace declaration?
- the <p> element cannot have a <div> element as a child (nor can a 
<div> element have a <p> element as a parent).

Is it possible my browsers have it right after all?

Regards,
David