[Python-bugs-list] [ python-Bugs-469772 ] support additional LINK elements.

[noreply@sourceforge.net]

Bugs item #469772, was opened at 2001-10-09 23:27
You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=105470&aid=469772&group_id=5470

Category: Documentation
Group: Feature Request
Status: Open
>Resolution: Fixed
Priority: 5
Submitted By: Anthony Baxter (anthonybaxter)
>Assigned to: Anthony Baxter (anthonybaxter)
Summary: support additional LINK elements.

Initial Comment:
Now that mozilla supports the LINK element properly, 
it would be most excellent if the python docs were 
generated with more LINK elements. 

At the moment they're built with up, previous, and next.
Some of the others are defined in 
http://www.w3.org/TR/REC-html40/types.html#type-links

Ones that would be very nice are Top, Contents and Index.



----------------------------------------------------------------------

>Comment By: Fred L. Drake, Jr. (fdrake)
Date: 2001-10-24 15:10

Message:
Logged In: YES 
user_id=3066

Anthony, what do you think of the current status on this? 
Do we need to worry about this further in the near future? 
I've marked it fixed but left it open & assigned to you;
please comment and either close or re-assign to me as
needed.  Thanks!

----------------------------------------------------------------------

Comment By: Fred L. Drake, Jr. (fdrake)
Date: 2001-10-22 14:27

Message:
Logged In: YES 
user_id=3066

The Mozilla bug I filed (see my previous comment) was
declared a duplicate of this bug:

http://bugzilla.mozilla.org/show_bug.cgi?id=102915


----------------------------------------------------------------------

Comment By: Fred L. Drake, Jr. (fdrake)
Date: 2001-10-22 10:05

Message:
Logged In: YES 
user_id=3066

OK, I've played with this a bit more, and I've modified the
transformation to support more <link> elements
(Doc/perl/l2hinit.perl revision 1.56), but the intended
semantics are still pretty fuzzy.

In particular, the links described seem to work within a
tree  which can share a single definition of these links
throughout.  Given that "top", "start", and "first" are not
well defined, it's not clear how to apply these.  The Python
documentation consists of a set of documents which each have
specific identities (the Library Reference, Python/C API
manual, etc.).  Does "start" refer to the front of an
individual manual or the collection?  How about "top"?  The
use of "document" to mean "page" in the W3C documents
doesn't help.

What I've done uses the title page of each document as the
"first" link, but doesn't provide the "top" link at all.

Mozilla also doesn't seem to understand that multiple
indexes are entirely valid; it should probably convert the
"Index" entry to a menu when there are multiple indexes --
I'll file a Mozilla bug report for this one.

----------------------------------------------------------------------

Comment By: Fred L. Drake, Jr. (fdrake)
Date: 2001-10-22 08:08

Message:
Logged In: YES 
user_id=3066

Added some support for the "up" link in Doc/tools/support.py
revision 1.4, but this only affects a couple of pages.

----------------------------------------------------------------------

Comment By: Anthony Baxter (anthonybaxter)
Date: 2001-10-18 08:46

Message:
Logged In: YES 
user_id=29957

There's a very nice list of what link relationships do 
what for mozilla 0.9.5 posted at: 
http://lists.w3.org/Archives/Public/www-html/2001Oct/0026.html

(link stolen from mozillazine)


----------------------------------------------------------------------

You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=105470&aid=469772&group_id=5470