From owner-freebsd-doc Fri Oct 15 3:21:12 1999 Delivered-To: freebsd-doc@freebsd.org Received: from vader.cs.berkeley.edu (vader.CS.Berkeley.EDU [128.32.38.234]) by hub.freebsd.org (Postfix) with ESMTP id 0C94215332; Fri, 15 Oct 1999 03:21:09 -0700 (PDT) (envelope-from asami@stampede.cs.berkeley.edu) Received: from silvia.hip.berkeley.edu (sji-ca1-150.ix.netcom.com [209.109.232.150]) by vader.cs.berkeley.edu (8.9.3/8.9.3) with ESMTP id DAA76655; Fri, 15 Oct 1999 03:21:07 -0700 (PDT) (envelope-from asami@stampede.cs.berkeley.edu) Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.9.3/8.6.9) id DAA10183; Fri, 15 Oct 1999 03:21:03 -0700 (PDT) To: Cc: freebsd-doc@FreeBSD.org Subject: Re: #anchors in .html handbook References: <199910151000.DAA20233@freefall.freebsd.org> From: asami@FreeBSD.org (Satoshi - Ports Wraith - Asami) Date: 15 Oct 1999 03:21:03 -0700 In-Reply-To: 's message of "Fri, 15 Oct 1999 03:00:20 -0700 (PDT)" Message-ID: Lines: 32 X-Mailer: Gnus v5.7/Emacs 20.4 Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org * From: Thanks for the explanation.... * 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). Eek. So it was the previous behavior that was wrong? (And may I (hypothetically) bang the head of the person who wrote that part of the standard to a really hard wall? Many times? HELLO?!?) * Now, the HTML 3.2 spec claims that using and * 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. * Yes, Netscape and Lynx don't seem to work correctly if anchor and * fragment names don't match exactly. However, links within the handbook 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 maybe you mean "correctly" in terms of in real life, like getting work done, as opposed to stiff-necked standards. This really sucks. I'm glad I didn't go into the field of documentation. :< Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message