discuss@mandoc.bsd.lv
 help / color / mirror / Atom feed
From: "Anthony J. Bentley" <anthonyjbentley@gmail.com>
To: discuss@mdocml.bsd.lv
Subject: Re: mandoc -Thtml cleanup
Date: Fri, 24 Dec 2010 17:08:23 -0700	[thread overview]
Message-ID: <4d1535fa.1b35640a.6a0c.ffffb6e2@mx.google.com> (raw)
In-Reply-To: <4D152AD8.9040300@bsd.lv>

Hi Kristaps,

> >> There's
> >> always that Table of Contents, which man.cgi generates but we don't...
> >
> > There are some link types that may be useful semantically for this kind
> > of thing:
> >
> > http://www.w3.org/TR/html401/types.html#type-links
> > http://www.w3.org/TR/html401/struct/links.html#h-12.3
> 
> Those look really cool!  Unfortunately, I don't see Firefox (for one) 
> actually using this data in any way---I could easily supply SECTION and 
> SUBSECTION fragment href's instead of having some clunky TOC, but that 
> doesn't get me anywhere if the links aren't listed.

There's an extension for that:
https://addons.mozilla.org/en-US/firefox/addon/2933/

Opera does have the buttons available. Also I believe that Opera will,
e.g., follow a <link rel="next"> if you hit space at the end of a page.
But yes, it's a real shame that most browsers don't have these easily
accessible to the user. They're neat features.

Search engines might use them as well but I don't know any details.

--
Hope this helps,
Anthony J. Bentley
--
 To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv

      reply	other threads:[~2010-12-25  0:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <201012222235.oBMMZ5ZA025569@cvs.openbsd.org>
     [not found] ` <20101222225049.GE1480@hera.home>
     [not found]   ` <20101223202724.GA8744@iris.usta.de>
2010-12-24 14:47     ` Kristaps Dzonsons
2010-12-24 18:41       ` Anthony J. Bentley
2010-12-24 23:20         ` Kristaps Dzonsons
2010-12-25  0:08           ` Anthony J. Bentley [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4d1535fa.1b35640a.6a0c.ffffb6e2@mx.google.com \
    --to=anthonyjbentley@gmail.com \
    --cc=discuss@mdocml.bsd.lv \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).