Date: Fri, 15 Oct 1999 03:00:20 -0700 (PDT) From: <jkoshy@FreeBSD.org> To: asami@FreeBSD.org Cc: freebsd-doc@FreeBSD.org Subject: Re: #anchors in .html handbook Message-ID: <199910151000.DAA20233@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>>>> "Satoshi Asami" <asami@FreeBSD.ORG> writes
> Has something changed in the handbook's # anchor generation? It
> appears everything is now changed into uppercase.
The HTML 3.2 spec specifies:
SYNTAX
...
NAMECASE GENERAL YES
ENTITY NO
...
From what I understand from reading the rather dense SGML standard,
this means that NAMEs, NAME TOKENs etc are to be mapped to upper-case,
but entity names aren't to be. An anchor target is a NAME (an ID
to be precise).
Now, the HTML 3.2 spec claims that using <a name="XXX"> and <a name="xxx">
in the same document is illegal, so one assumes that anchor ids should
be treated as case insensitive. However it also says that the behaviour
of user agents when fragment names and anchor names are not case-exact
is undefined.
This is a little confusing ...
> Needless to say, this breaks a whole bunch of web pages that specify
> sections in the handbook. (I just found it out when I couldn't get to
> the correct section in the handbook from my package building error
> logs page.)
Yes, Netscape and Lynx don't seem to work correctly if anchor and
fragment names don't match exactly. However, links within the handbook
will internally consistent.
Regards,
Koshy
<jkoshy@freebsd.org>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-doc" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199910151000.DAA20233>