From: Jason McIntyre <jmc@kerhand.co.uk>
To: schwarze@usta.de
Cc: discuss@mdocml.bsd.lv
Subject: Re: Where to put mandoc roff documentation?
Date: Sat, 27 Nov 2010 21:18:08 +0000 [thread overview]
Message-ID: <20101127211832.GA27550@kerhand.co.uk> (raw)
In-Reply-To: <20101127184503.GA27534@iris.usta.de>
On Sat, Nov 27, 2010 at 07:45:03PM +0100, Ingo Schwarze wrote:
> Hi Jason,
>
> i'm looking for your advice regading the question how to organize
> mandoc roff documentation. By that term, i'm referring to man pages
> explaining:
>
> 1. Common features of the mdoc(7) and man(7) languages
> being common because they are actually features of the roff
> language - currently, there is quite some duplication.
> Topics include:
> - basic request and macro syntax
> - permitted input characters
> - comment syntax
> - predefined special characters and strings
> - predefined escape sequences, for example regarding text decoration
> - basics of whitespace handling
> - scaling widths
> - end-of-sentence spacing
>
> 2. Common macros
> being common because they are actually roff macros or even
> roff requests, for example:
> - .br
> - .sp
>
> 3. Low-level roff requests that are not mdoc(7) or man(7) macros,
> for example:
> - .de
> - .ds
> - .if
> - .ig
> - .nr
> - .rm
> - .rn
> - .so
> And also:
> - user-defined macros
> - user-defined strings
>
> 4. Common aspects of the usage of the mdoc(7) and man(7) languages
> being common because they do not depend on the language at all.
> Topics include:
> - manual sections
> - general advice about writing manuals
>
> In particular, running mandoc -Tlint on Perl, Xenocara, and typical
> ports manuals, i expect improving low-level roff support will be the
> focus of mandoc development in the near future. Hence, most of the
> new documentation to be written will probably be category 3, and
> perhaps some 2.
>
> I consider moving roff.7 from /usr/src/usr.bin/mandoc/
> to /usr/src/share/man/man7/ and getting it ready for installation
> by moving documentation of the categories 1, 2 and 3 into it.
> But i'm not 100% sure whether all of this - with the exception
> of mandoc_char(7), of course - should really go into the same
> document.
>
> I'm also hesitant regarding the name. The current name roff(7) seems
> fitting on the one hand, because this document would indeed document
> features of the roff language, and nothing else. On the other hand,
> that name feels presumptuous, because we will hardly ever document
> the roff language as a whole, and because calling it roff(7) would
> hide the rather interesting roff(7) manual once we update our
> groff port to a recent version, see:
>
> http://www.manpagez.com/man/7/roff/
>
> Yet on the other hand, even though that document is interesting,
> it is perhaps named badly and should be installed as roff_history(7),
> or not at all, because however interesting, it is not a real manual.
>
> Finally, i feel quite at a loss about what to do with category 4.
> Maybe move it to a manuals(7) manual, like the one Kristaps once
> started, and .Xr to it? Or leave it in mdoc(7), because that's
> where we send people writing new manuals, and point to it from
> man(7)? Or just maintain two copies for good?
>
> Thoughts?
>
> Yours,
> Ingo
> --
> To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv
it sounds like one page is a good idea for this stuff - roff, troff,
whatever. i wouldn;t worry about squashing a groff page - the port could
be tweaked to install under a different name.
so i;d say yes, stick 1, 2, and 3 in a roff page.
if there's stuff more suited to mdoc (or repeated), i'd leave it in mdoc
and have roff point to it (i.e. point 4).
we don;t have to worry too much - if it evolves into something else, we
can change it in the future.
jmc
--
To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv
next prev parent reply other threads:[~2010-11-27 21:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-27 18:45 Ingo Schwarze
2010-11-27 21:18 ` Jason McIntyre [this message]
2010-11-27 21:46 ` Ingo Schwarze
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=20101127211832.GA27550@kerhand.co.uk \
--to=jmc@kerhand.co.uk \
--cc=discuss@mdocml.bsd.lv \
--cc=schwarze@usta.de \
/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).