Re: An Anchor attribute question:
ccoprmm@oit.gatech.edu (Michael Mealling)
Errors-To: listmaster@www0.cern.ch
Date: Thu, 2 Jun 1994 17:25:04 +0200
Errors-To: listmaster@www0.cern.ch
Message-id: <199406021522.AA19445@oit.gatech.edu>
Errors-To: listmaster@www0.cern.ch
Reply-To: ccoprmm@oit.gatech.edu
Originator: www-talk@info.cern.ch
Sender: www-talk@www0.cern.ch
Precedence: bulk
From: ccoprmm@oit.gatech.edu (Michael Mealling)
To: Multiple recipients of list <www-talk@www0.cern.ch>
Subject: Re: An Anchor attribute question:
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
Content-Type: text/plain; charset=US-ASCII
Content-Type: text/plain; charset=US-ASCII
Mime-Version: 1.0
Mime-Version: 1.0
X-Mailer: ELM [version 2.4 PL23]
X-Mailer: ELM [version 2.4 PL23]
Daniel W. Connolly said this:
> In message <199406021352.AA15799@oit.gatech.edu>, Michael Mealling writes:
> >My example would be more like this:
> >
> >See <A URN="URN:IANA:IETF:rfc/822"> The Format for Internet Messages</A>
> >for more information.
>
> Actually, now that I think about it, If you're not going to include
> a redundant URL, why don't you just write:
>
> <A HREF="URN:IANA:IETF:rfc/822"> ...</a>
>
> ???
This would work also. I would like to be able to make this distinction
in HTML though. Simply to keep in the spirit. There also seems to be
something in HTParse.c that is causing that example URN to be invalid
since HTParse.c: scan() function makes the assumption (which may be
a correct one according to the current URL spec) that no other colon
should exist beyond the first one. This is causing HTParse() to turn
the above into "URN:rfc/822" by basically looking at the first colon
READING BACKWARDS.
Is this correct?
--
------------------------------------------------------------------------------
<HR><A HREF="http://www.gatech.edu/michael.html">
<ADDRESS>Michael Mealling</ADDRESS>
<ADDRESS>michael.mealling@oit.gatech.edu</ADDRESS></A>