From: Eli Zaretskii <eliz@gnu.org>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: jeremy.bennett@embecosm.com, gdb@sourceware.org
Subject: Re: Documentation generated from sources proposal
Date: Tue, 13 Oct 2009 19:18:00 -0000 [thread overview]
Message-ID: <83iqejhzj7.fsf@gnu.org> (raw)
In-Reply-To: <20091013191301.GA24733@host0.dyn.jankratochvil.net>
> Date: Tue, 13 Oct 2009 21:13:01 +0200
> From: Jan Kratochvil <jan.kratochvil@redhat.com>
> Cc: jeremy.bennett@embecosm.com, gdb@sourceware.org
>
> On Tue, 13 Oct 2009 20:18:28 +0200, Eli Zaretskii wrote:
> > No, the format generated from the comments must be Texinfo.
>
> Are there some specific technical or FSF reasons?
Both. The GNU Project writes documentation in Texinfo, and if I need
to be responsible for the GDB manuals, I need to be an expert in the
language we use to write them.
> I freely admit a side track of my proposal was to be able to start writing the
> doc in a different format than texinfo.
I don't see a need to start that battle. Texinfo is more than
adequate for GDB, IMO.
> Still a .c-placed doc even in the texinfo format I find a useful improvement.
Yes, of course.
next prev parent reply other threads:[~2009-10-13 19:18 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
2009-10-13 19:13 ` Jan Kratochvil
2009-10-13 19:18 ` Eli Zaretskii [this message]
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=83iqejhzj7.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