public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Grant Edwards <grant.b.edwards@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: writing man pages (gentoo conventions)
Date: Wed, 3 Jun 2015 15:21:15 +0000 (UTC)	[thread overview]
Message-ID: <mkn61b$v1m$1@ger.gmane.org> (raw)
In-Reply-To: 10241300.5UVIySPyLa@wstn

On 2015-06-03, Peter Humphrey <peter@prh.myzen.co.uk> wrote:
> On Wednesday 03 June 2015 14:24:18 Grant Edwards wrote:
>> On 2015-06-03, Martin Vaeth <martin@mvath.de> wrote:
>> > James <wireless@tampabay.rr.com> wrote:
>> >> So instead of my spew of ascii information files, I'm now composing
>> >> 'man pages' mostly using txt2man.
>> > 
>> > If you want to avoid learning *roff, there is also e.g. pod from perl
>> > which gives you simple basic markup functionality and can output in
>> > man page format (and other format).
>> 
>> asciidoc, markdown, and reStructuredText can all generate man page
>> format as well as HTML, PDF, and others.  The main benefit of these is
>> that they're also easy to read in their "raw" input format (unlike
>> roff).
>
> Isn't there a Gentoo Way too? I can't put my finger on it just now
> but I think I've seen a reference to producing Gentoo docs, including
> man pages.

The only thing I know of is GuideXML which is used to generate the
user guide:

  https://wwwold.gentoo.org/doc/en/xml-guide.xml

I'm not aware of it generating anything other than docbook or HTML,
but maybe you could use something like this to then convert from
docbook to man:

https://www.oasis-open.org/docbook/tools/dtm/
  
-- 
Grant Edwards               grant.b.edwards        Yow! I hope something GOOD
                                  at               came in the mail today so
                              gmail.com            I have a REASON to live!!



  reply	other threads:[~2015-06-03 15:21 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-03  4:21 [gentoo-user] writing man pages (gentoo conventions) James
2015-06-03  5:57 ` Alan McKinnon
2015-06-03 11:03 ` [gentoo-user] " Martin Vaeth
2015-06-03 11:13   ` Joerg Schilling
2015-06-03 15:29     ` James
2015-06-03 15:53       ` Joerg Schilling
2015-06-03 14:24   ` Grant Edwards
2015-06-03 15:14     ` Peter Humphrey
2015-06-03 15:21       ` Grant Edwards [this message]
2015-06-03 15:31       ` Jc GarcĂ­a
2015-06-03 15:34     ` James
2015-06-03 15:49       ` Marc Joliet
2015-06-03 15:59       ` Grant Edwards
2015-06-03 16:02         ` Joerg Schilling
2015-06-03 15:25   ` James
2015-06-04 16:48     ` Martin Vaeth

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='mkn61b$v1m$1@ger.gmane.org' \
    --to=grant.b.edwards@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /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