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 11:41:54 -0700	[thread overview]
Message-ID: <4d14e976.0aeb640a.6fa9.ffffb4b9@mx.google.com> (raw)
In-Reply-To: <4D14B277.6070204@bsd.lv>

Hi Kristaps,

I'm really happy to see the improved HTML output of mandoc. It really
looks great compared to the <div> output from before.

I notice there's a redundant 'font-family: monospace;' declaration in
style.css that is immediately overwritten with 'font-family: Times, serif;':
http://mdocml.bsd.lv/cgi-bin/cvsweb/style.css?rev=1.19&content-type=text/x-cvsweb-markup&cvsroot=mdocml

> example, to tag function prototypes and utility syntaxes in the SYNOPSIS 
> section with an A NAME, then link up to them from within the document 

FYI, A NAME and A ID are more-or-less interchangeable, and you might want
to use ID for consistency since mandoc uses IDs elsewhere. Or not, since
there's almost no difference between the two.

http://www.w3.org/TR/html401/struct/links.html#h-12.2.3

> 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

I do think it would be funny to see mdoc beat texinfo at its own game
(namely, hyperlinking)! ;)

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

  reply	other threads:[~2010-12-24 18:42 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 [this message]
2010-12-24 23:20         ` Kristaps Dzonsons
2010-12-25  0:08           ` Anthony J. Bentley

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=4d14e976.0aeb640a.6fa9.ffffb4b9@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).