From: Eli Zaretskii <eliz@gnu.org>
To: jeremy.bennett@embecosm.com
Cc: jan.kratochvil@redhat.com, gdb@sourceware.org
Subject: Re: Documentation generated from sources proposal
Date: Tue, 13 Oct 2009 18:16:00 -0000 [thread overview]
Message-ID: <83ljjfi2dn.fsf@gnu.org> (raw)
In-Reply-To: <1255422217.4479.47.camel@thomas>
> From: Jeremy Bennett <jeremy.bennett@embecosm.com>
> Cc: Jan Kratochvil <jan.kratochvil@redhat.com>, gdb@sourceware.org
> Date: Tue, 13 Oct 2009 09:23:37 +0100
>
> One suggestion: gtk-doc is not that general purpose. Doxygen (as
> recommended by the gtk-doc website) might prove a more flexible
> alternative.
>
> The one caveat is that neither of these programs can generate Texinfo,
> so generating .info files will be hard (all the other output formats,
> including man pages can be generated directly, at least by Doxygen). In
> principle it could be done (gtk-doc->docbook->texinfo->info or
> doxygen->XML->texinfo->info), but who knows what the output might end up
> like!
No, the format generated from the comments must be Texinfo.
Can't we use whatever libiberty is using (gather-doc), and format the
comments as it does? Why do we need to switch to such drastically
different tools?
next prev parent reply other threads:[~2009-10-13 18:16 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-12 16:14 Jan Kratochvil
2009-10-12 17:12 ` Tom Tromey
2009-10-12 17:16 ` Jan Kratochvil
2009-10-12 18:00 ` Daniel Jacobowitz
2009-10-12 18:07 ` Jan Kratochvil
2009-10-12 18:13 ` Daniel Jacobowitz
2009-10-12 18:20 ` Jan Kratochvil
2009-10-12 18:26 ` Tom Tromey
2009-10-12 18:30 ` Jan Kratochvil
2009-10-12 18:54 ` Eli Zaretskii
2009-10-12 19:10 ` Daniel Jacobowitz
2009-10-12 19:25 ` Tom Tromey
2009-10-12 20:23 ` Eli Zaretskii
2009-10-12 18:57 ` Eli Zaretskii
2009-10-13 8:23 ` Jeremy Bennett
2009-10-13 18:16 ` Eli Zaretskii [this message]
2009-10-13 19:13 ` Jan Kratochvil
2009-10-13 19:18 ` Eli Zaretskii
2009-10-27 10:07 ` Mark Kettenis
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=83ljjfi2dn.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=jeremy.bennett@embecosm.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