From: Steinar Bang <sb@dod.no>
To: gdb@sourceware.org
Subject: Re: A new strategy for internals documentation
Date: Wed, 21 Aug 2013 18:09:00 -0000 [thread overview]
Message-ID: <87wqne9ar5.fsf@dod.no> (raw)
In-Reply-To: <5202A6D6.8090908@earthlink.net>
>>>>> Stan Shebs <stanshebs@earthlink.net>:
>>> *** Doxygen
>>> As a second step, we should adopt Doxygen for the sources, and use it
>>> to generate material for a new area of the website, which will be the
>>> detailed documentation of GDB internals.
>> AFAIK, Doxygen cannot generate an Info manual, only HTML. If so, this
>> would be a serious downside that you don't mention.
> Hmm, I'm perhaps prejudiced since I haven't looked at any info file in
> probably a decade. Are many people using them still?
Doxygen can generate output in Docbook XML. A quick google found me
this tool that can convert Docbook to texinfo:
http://docbook2x.sourceforge.net/
How well that works I have no idea.
The Docbook output can be converted to a printable manual, and so can
Doxygen's LaTeX output.
next prev parent reply other threads:[~2013-08-21 18:09 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-06 22:26 Stan Shebs
2013-08-07 4:28 ` Eli Zaretskii
2013-08-07 19:58 ` Stan Shebs
2013-08-08 17:28 ` Eli Zaretskii
2013-08-08 21:08 ` Doug Evans
2013-08-08 21:56 ` Eli Zaretskii
2013-08-08 23:03 ` Stan Shebs
2013-08-09 8:08 ` John Gilmore
2013-08-09 9:53 ` Eli Zaretskii
2013-08-09 9:35 ` Eli Zaretskii
2013-08-09 23:04 ` Stan Shebs
2013-08-09 9:53 ` Mark Kettenis
2013-08-09 23:28 ` Stan Shebs
2013-08-08 23:04 ` Doug Evans
2013-08-09 9:13 ` Eli Zaretskii
2013-08-10 1:13 ` Yao Qi
2013-08-21 18:09 ` Steinar Bang [this message]
2013-08-21 20:02 ` Eli Zaretskii
2013-08-22 18:29 ` Steinar Bang
2013-08-08 3:45 ` Yao Qi
2013-08-08 17:31 ` Eli Zaretskii
2013-08-09 1:30 ` John Gilmore
2013-08-09 9:26 ` Eli Zaretskii
2013-08-09 18:16 ` Tom Tromey
2013-08-09 18:36 ` Eli Zaretskii
2013-08-09 22:31 ` Stan Shebs
2013-08-09 23:32 ` Matt Rice
2013-08-10 2:24 ` John Gilmore
2013-08-08 20:43 ` Tom Tromey
2013-08-08 20:57 ` Doug Evans
2013-08-08 20:41 ` Tom Tromey
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=87wqne9ar5.fsf@dod.no \
--to=sb@dod.no \
--cc=gdb@sourceware.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