From owner-freebsd-doc  Fri Oct 15  4:50:15 1999
Delivered-To: freebsd-doc@freebsd.org
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
	by hub.freebsd.org (Postfix) with ESMTP
	id EC3281531B; Fri, 15 Oct 1999 04:50:13 -0700 (PDT)
	(envelope-from jkoshy@FreeBSD.org)
Received: (from jkoshy@localhost)
	by freefall.freebsd.org (8.9.3/8.9.2) id EAA30422;
	Fri, 15 Oct 1999 04:50:13 -0700 (PDT)
	(envelope-from jkoshy@FreeBSD.org)
Date: Fri, 15 Oct 1999 04:50:13 -0700 (PDT)
From: <jkoshy@FreeBSD.org>
Message-Id: <199910151150.EAA30422@freefall.freebsd.org>
X-Mailer: exmh version 2.0.2 2/24/98
To: asami@FreeBSD.org (Satoshi - Ports Wraith - Asami)
Cc: freebsd-doc@FreeBSD.org
Subject: Re: #anchors in .html handbook 
In-Reply-To: Your message of "15 Oct 1999 03:21:03 MST."
             <vqczoxkx6uo.fsf@silvia.hip.berkeley.edu> 
Mime-Version: 1.0
Content-Type: text/plain
Sender: owner-freebsd-doc@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org



> Eek.  So it was the previous behavior that was wrong?  (And may I

A small correction: I had assumed that the 'name' attribute for
<A> was parsed as an ID.  A perusal of the HTML declaration however
shows that it has been declared as CDATA and is thus is not under
the scope of the NAMING case conversion rules.

Further the HTML 3.2 spec also says:

<--http://www.w3.org/TR/REC-html40/struct/links.html#h-12.2-->
o Uniqueness: Anchor names must be unique within a document. Anchor
  names that differ only in case may not appear in the same document.

o String matching: Comparisons between fragment identifiers and
  anchor names must be done by exact (case-sensitive) match.
<---->

In itself this is consistent because 'name' attributes are parsed as
CDATA (not ID as I assumed earlier) as are 'href' attributes.  These 
are thus case *sensitive* (subject to the above rules) and work well
together.

> I'm not sure if I follow you here, the standard says user agents are
> not required to do anything special for non-case-matching names, so
> Netscape (the one I tried) is perfectly following the standard.  But

Yes, Netscape and Lynx are behaving correctly.  

We are generating <A> anchors based on the 'id' attributes of the
original docbook elements.  Since 'id's seem to be getting mapped to 
upper case the generated anchors also get to be in upper case.

Perhaps someone with more SGML knowledge will clarify.  

Koshy
<jkoshy@freebsd.org>




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-doc" in the body of the message