public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Florian Weimer <fw@deneb.enyo.de>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: ada/5907: The Ada front end lacks a proper manual
Date: Sun, 10 Mar 2002 03:36:00 -0000 [thread overview]
Message-ID: <20020310113602.10093.qmail@sources.redhat.com> (raw)
The following reply was made to PR ada/5907; it has been noted by GNATS.
From: Florian Weimer <fw@deneb.enyo.de>
To: "Joseph S. Myers" <jsm28@cam.ac.uk>
Cc: <gcc-gnats@gcc.gnu.org>, <gcc-bugs@gcc.gnu.org>, brosgol@gnat.com
Subject: Re: ada/5907: The Ada front end lacks a proper manual
Date: Sun, 10 Mar 2002 12:34:50 +0100
"Joseph S. Myers" <jsm28@cam.ac.uk> writes:
> On 10 Mar 2002 fw@deneb.enyo.de wrote:
>
>> Add the User Guide to the tree. Florian Weimer is working on an Ada
>> version of the preprocessor which is required to generate proper
>> Texinfo files.
>
> It is desirable if possible that preprocessing is done within Texinfo (via
> Texinfo manuals).
The VMS version requires substantial postprocessing (words are
replaced globally, file names are rewritten). It is not possible to
express this in Texinfo.
I think it would be possible to change the manual so that you can
build all the other version straight from the Texinfo sources,
but this might reduce maintainability. There would be two rather
different ways to build the manual, the Texinfo markup would be a
bit clumsy, and the TeX implementation of Texinfo doesn't handle
extensive use of conditional processing and macros very well. On the
other hand, having the generated sources in CVS is ugly and prone to
problems.
Ben, what do you think?
next reply other threads:[~2002-03-10 11:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-10 3:36 Florian Weimer [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-10-06 2:26 Joseph S. Myers
2002-10-05 16:38 bosch
2002-03-10 11:36 Florian Weimer
2002-03-10 11:06 Joseph S. Myers
2002-03-10 6:16 Florian Weimer
2002-03-10 3:56 Joseph S. Myers
2002-03-10 3:06 Joseph S. Myers
2002-03-10 2:06 fw
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=20020310113602.10093.qmail@sources.redhat.com \
--to=fw@deneb.enyo.de \
--cc=gcc-prs@gcc.gnu.org \
--cc=nobody@gcc.gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).