W3C home > Mailing lists > Public > spec-prod@w3.org > July to September 2005

RE: Spurious <a> elements in xmlspec.xsl

From: Richard Ishida <ishida@w3.org>
Date: Wed, 13 Jul 2005 19:48:37 +0100
To: "'Richard Ishida'" <ishida@w3.org>, <spec-prod@w3.org>
Cc: "'Felix Sasaki'" <fsasaki@w3.org>
Message-Id: <20050713184834.9311B4EFE7@homer.w3.org>

Aha!  It seems to be a weird bug in Firefox.  When I view selected source or show information (Display & Class details) it shows these extra <a> anchors, but not when I do normal view source, or look at the source using notepad.

Phew, panic over.

RI


============
Richard Ishida
W3C

contact info:
http://www.w3.org/People/Ishida/ 

W3C Internationalization:
http://www.w3.org/International/ 

Publication blog:
http://people.w3.org/rishida/blog/
 
 

> -----Original Message-----
> From: Richard Ishida [mailto:ishida@w3.org] 
> Sent: 13 July 2005 17:57
> To: spec-prod@w3.org
> Cc: 'Richard Ishida'
> Subject: Spurious <a> elements in xmlspec.xsl 
> 
> I'm finding that spurious <a> elements are being created when 
> I run xmlspec.xsl using Saxon.
> 
> For example, see how the anchor on the h3 is cascaded to 
> several p elements following:
> 
> <h3><a name="d2e325" id="d2e325">3.3 Relationships with 
> character encoding and directionality</a></h3> <p><a 
> name="d2e325" id="d2e325">'<span class="qterm">Character 
> encoding</span>' refers to the bytes that are used to 
> represent characters in text. It is important to declare what 
> encoding is being used for your document.</a></p> <p><a 
> name="d2e325" id="d2e325">In some scripts, such as Arabic and 
> Hebrew, text runs predominantly from right to left. Within 
> that flow, numbers and text from other scripts run from left 
> to right. It is important to adequately specify the intended 
> '<span class="qterm">directionality</span>' of text in a 
> document.</a></p> <p><a name="d2e325" 
> id="d2e325"><em>Language declarations in HTML and XHTML have 
> nothing to do with character encoding or the direction of 
> text.</em>...
> 
> This is really weird.  It also happens with other element 
> combinations after a call to the anchor template in the 
> initial element. Anyone got any clues how to fix it?
> 
> RI
> 
> 
> ============
> Richard Ishida
> W3C
> 
> contact info:
> http://www.w3.org/People/Ishida/ 
> 
> W3C Internationalization:
> http://www.w3.org/International/ 
> 
> Publication blog:
> http://people.w3.org/rishida/blog/
>  
> 
Received on Wednesday, 13 July 2005 18:48:42 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 10 March 2012 06:19:13 GMT