From: Hans Deragon <hans@deragon.biz>
Cc: docbook-tools-discuss@sources.redhat.com
Subject: Re: Creating man pages from Docbook - docbook2man does not generate man pages.
Date: Mon, 17 Nov 2003 17:31:00 -0000 [thread overview]
Message-ID: <3FB905C0.2010102@deragon.biz> (raw)
In-Reply-To: <20031117171720.GC540@redhat.com>
Tim Waugh wrote:
> On Mon, Nov 17, 2003 at 12:04:53PM -0500, Hans Deragon wrote:
>
>
>> Newbie here with docbook. Docbook is easy and I get docbook2pdf,
>> docbook2ps and docbook2html working marvelously. However, when I run
>>docbook2man, only the following two files are created:
>>
>>-rw-r--r-- 1 qhander qhander 0 Nov 17 11:11 manpage.links
>>-rw-r--r-- 1 qhander qhander 27 Nov 17 11:11 manpage.refs
>>
>> There is no real man page created. I search for the web for some HowTos,
>> but no success. What is missing to generate man pages?
>
>
> Perhaps you don't have any <refentry> elements?
>
> Tim.
> */
Thanks for the tip, but could you point me to a howto for creating man pages
with docbook? Is it actually possible from a same docbook xml to create man
pages and a normal pdf document? Or must I have one special docbook for man
pages and another one for the other formats? Ideally, I want to be able to
generate a nice PDF manual and a man page from the same source, without having
to duplicate text.
Sincerely,
Hans Deragon
--
Consultant en informatique/Software Consultant
Deragon Informatique inc. Open source:
http://www.deragon.biz http://swtmvcwrapper.sourceforge.net
mailto://hans@deragon.biz http://autopoweroff.sourceforge.net
next prev parent reply other threads:[~2003-11-17 17:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-17 17:06 Hans Deragon
2003-11-17 17:17 ` Tim Waugh
2003-11-17 17:31 ` Hans Deragon [this message]
2003-11-17 17:40 ` Tim Waugh
2003-11-17 18:29 ` John Fleck
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=3FB905C0.2010102@deragon.biz \
--to=hans@deragon.biz \
--cc=docbook-tools-discuss@sources.redhat.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).