[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

LYNX-DEV Lynx and the LINK tag.

From: Subir Grewal
Subject: LYNX-DEV Lynx and the LINK tag.
Date: Thu, 23 Jan 1997 19:37:08 -0800 (PST)

A few notes on Lynx's handling of LINK tags.  After reading Peter's note
(that Lynx may not be handling all the standardized LINK REL/REV
attributes) I was curious enough to glance at the Lynx code to see what
was happening with LINK, I found it handles a lot more rel attributes than
I thought it did, though I'm not sure whether it handles all of the
standardized ones (but Fote's note gives me the impression these are all
the attributes defined in the DTDs for 3.0 and 3.2).  Here's my
analysis of the scenario based on a cursory glance at the source code [1] 

-----Begin snippet from src/HTML.c-----

                 *  Ignore anything not registered in the the 28-Mar-95
                 *  IETF HTML 3.0 draft and W3C HTML 3.2 draft, or not
                 *  appropriate for Lynx banner links in the expired
                 *  Maloney and Quin relrev draft.  We'll make this more
                 *  efficient when the situation stabilizes, and for now,
                 *  we'll treat "Banner" as another toolbar element. - FM

-----End snippet from src/HTML.c-----

Now, extrapolating from the code that follows, I see that Lynx handles the
following REL attributes for the LINK tag (basically creating a toolbar,
using the attribute value as the linked text and the href value as the
href for the linki.  If there's no href the tag is ignored). 

Home ToC Contents Index Glossary Copyright Up Next Previous Prev Help
Bookmark Banner Top Origin Navigator Child Disclaimer Sibling Parent
Author Editor Publisher Trademark Meta Begin First End Last Pointer
Translation Bibliography

In addition it does something special with the following REL attributes:

Home Help Index

And Lynx recognizes the following REV attributes:

owner made title

(Owner is used while constructing the info '=' page, as far as I know
that's equivalent to <!-- Owner_Name="some_text">, which is what I use). 
As others have noted, it uses the href attribute (if it's a mailto: URL) 
of a LINK REV=made to provide an easy mechanism to mail c'omments to the

Another brief note has to do with the manner in which Lynx constructs the
toolbar.  It's true that the toolbar is only a keyclick away (the magic
key is '#'), but it doesn't stay on the screen all the time, I think Fote
though that would be inefficient when mose people are working with 24
lines (I agree of course).

Peter, If any standard LINK REV/REL attributes are not being handled by
Lynx, I'm sure the Lynx Developers would appreciate a little note to that
effect.  In my experience, Fote and the others have always been very
forthcoming at incorporating handling for standardized/commonly-used

[1] Since I don't speak/write C, I may have misunderstood some of the
code, but I think I'm right in my interpretation especially since the Lynx
code is so wonderfully self-documented.

address@hidden  +  Lynx 2.6  +  PGP  +
"This is a country where people are free to practice their religion,
regardless of race, creed, color, obesity, or number of dangling
keys ..."

; To UNSUBSCRIBE:  Send a mail message to address@hidden
;                  with "unsubscribe lynx-dev" (without the
;                  quotation marks) on a line by itself.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]