From: Michael Still <mikal@stillhq.com>
To: Andries Brouwer <aebr@win.tue.nl>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Sam Ravnborg <sam@ravnborg.org>,
Linus Torvalds <torvalds@osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
steve@ggi-project.org
Subject: Re: [PATCH] docbook: Added support for generating man files
Date: Sat, 19 Jul 2003 17:25:32 +1000 [thread overview]
Message-ID: <Pine.LNX.4.44.0307191721350.1829-100000@diskbox.stillhq.com> (raw)
In-Reply-To: <20030719091919.A3236@pclin040.win.tue.nl>
On Sat, 19 Jul 2003, Andries Brouwer wrote:
> On Sat, Jul 19, 2003 at 12:47:31PM +1000, Michael Still wrote:
>
> You do this in two steps: first construct an sgml document, then invoke
> docbook2man.
Which is what I currently do.
> So, first you have to figure out what the proper docbook markup is
> for such material. According to me it is <docinfo>...</docinfo>,
> to be placed inside <refentry> before <refmeta>.
> So you do that - example script fragments appended below.
I tried this...
> Next, the docbook2man stage. My presently installed docbook2man says
>
> # IGNORE.
> sgml('<DOCINFO>', sub { push_output('nul'); });
> sgml('</DOCINFO>', sub { pop_output(); });
>
> That is, it does not produce any output for a docinfo section.
...and hit this. Another option is that we could ship a tweaked version of
docbook2man with the kernel sources, and call that copy. That could then
turn docinfo's into comments -- this was what I was getting at with my
previous message.
> In the meantime I do not worry too much about this missing copyright.
Okie, that's fair enough.
> By the way, you start copying at <legalnotice>, but I consider that
> the least interesting part. The fact that these docs were written
> by Alan Cox is much more interesting. In other words, it might be
> a good idea to enlarge this <docinfo> section a bit.
Cool. I like your comments. I've got people coming over for dinner
tonight, but I'll see what I can do about whipping up a new patch.
Cheers,
Mikal
--
Michael Still (mikal@stillhq.com) | Stage 1: Steal underpants
http://www.stillhq.com | Stage 2: ????
UTC + 10 | Stage 3: Profit
next prev parent reply other threads:[~2003-07-19 7:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-18 20:48 [PATCH] docbook: Added support for generating man files Sam Ravnborg
2003-07-18 21:23 ` Sam Ravnborg
2003-07-18 21:54 ` Alan Cox
2003-07-18 22:36 ` Michael Still
2003-07-18 22:48 ` Andries Brouwer
2003-07-19 2:47 ` Michael Still
2003-07-19 7:19 ` Andries Brouwer
2003-07-19 7:25 ` Michael Still [this message]
2003-07-19 7:40 ` Sam Ravnborg
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=Pine.LNX.4.44.0307191721350.1829-100000@diskbox.stillhq.com \
--to=mikal@stillhq.com \
--cc=aebr@win.tue.nl \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.org \
--cc=steve@ggi-project.org \
--cc=torvalds@osdl.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;
as well as URLs for NNTP newsgroup(s).