tech@mandoc.bsd.lv
 help / color / mirror / Atom feed
From: Kristaps Dzonsons <kristaps@bsd.lv>
To: Jason McIntyre <jmc@cava.myzen.co.uk>
Cc: tech@mdocml.bsd.lv
Subject: Re: [PATCH] mdoc.7 tweaks.
Date: Wed, 06 Apr 2011 15:15:39 +0200	[thread overview]
Message-ID: <4D9C677B.2010804@bsd.lv> (raw)
In-Reply-To: <20110406124016.GF7870@harkle.bramka>

>>>> Jason, thanks for your feedback.  Enclosed is a corrected patch with the
>>>> exception of the following:
>>>>
>>>>>> -This expands upon the brief, one line description in
>>>>>> -.Em NAME .
>>>>>> -It usually contains a breakdown of the options (if documenting a
>>>>>> +This begins with an expansion of the brief, one line description in
>>>>>> +.Em NAME :
>>>>>
>>>>> you should use Sx to refer to other section names.
>>>>
>>>> We don't have section documentation `Ss'd, so I can't refer back to them
>>>> as such.  The reason being that we stipulate (in both `Ss' and `Sh'
>>>> documentation) that names should be unique, so I can't `Ss NAME'.
>>>>
>>>> On the other hand, I agree that `Em' is not a good choice.  Do you have
>>>> another suggestion?  (Note that using `It Em NAME' to document and refer
>>>> to per-section documentation has long since irritated me.)
>>>>
>>>
>>> hmm. we really only have Em and Sy to play around with in cases like
>>> this. i guess it's just a matter of preference. i have none in
>>> particular...
>>
>> How about `Ss NAME Section' or something similar?  Anything but
>> standalone NAME.  In fact, I'd far prefer something like this than an
>> opaque `Sy NAME' or whatnot.  Thoughts?
>
> i think that would just look messy. you could try, but i'm not
> convinced. many things don;t fit specific macros very well - i don;t see
> the point of worrying about it.

Jason (note re-posting to tech@),

Enclosed is a patch (the prior has been committed) that does just this 
and makes the `Em's used for table headers be `Sy'.  It also notes the 
difference between a "manual section" and a "section" (in my opinion, we 
should really change the term "manual section" to "category" or something).

This uses the schema of "XXXX section" for section documentation, and 
allows the manual to refer directly to this documentation.  Quite handy.

Thoughts?  If you're ambivalent, I note that this makes linked output 
(-T[x]html and -Tpdf/-Tps, which I'd like to implement) much more 
reference-friendly.

Kristaps
--
 To unsubscribe send an email to tech+unsubscribe@mdocml.bsd.lv

  parent reply	other threads:[~2011-04-06 13:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-06  9:47 Kristaps Dzonsons
     [not found] ` <20110406104809.GD7870@harkle.bramka>
2011-04-06 11:14   ` Kristaps Dzonsons
     [not found]     ` <20110406112651.GE7870@harkle.bramka>
     [not found]       ` <4D9C4E84.7080809@bsd.lv>
     [not found]         ` <20110406124016.GF7870@harkle.bramka>
2011-04-06 13:15           ` Kristaps Dzonsons [this message]
2011-04-06 13:20             ` Kristaps Dzonsons

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=4D9C677B.2010804@bsd.lv \
    --to=kristaps@bsd.lv \
    --cc=jmc@cava.myzen.co.uk \
    --cc=tech@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).