From: Geert Bosch <bosch@gnat.com>
To: guerby@acm.org
Cc: gcc@gcc.gnu.org
Subject: Re: [Ada] User Guide?
Date: Sat, 01 Dec 2001 19:52:00 -0000 [thread overview]
Message-ID: <022D9B00-E6D8-11D5-A27C-00039344BF4A@gnat.com> (raw)
In-Reply-To: <200112011134.fB1BYNA16933@ulmo.localdomain>
On Saturday, December 1, 2001, at 06:34 , <guerby@acm.org> wrote:
> I was just making a pass at the available Ada documentation and found
> only the GNAT Reference Manual in CVS (gnat_rm.texi). Is there any
> reason why the User Guide (gnat_ug.texi) is not in there yet? If
> it's just some stupid formatting to do, I volunteer, just drop me the
> file (IIRC I did the original SGI framemaker to texinfo pass, this will
> close the loop :).
Yes, that is the reason. In particular, we have preprocessing done
in order to get correct VMS documentation. This involves replacing
mentions of UNIX-style options by VMS-style long ones and a number
of other things. The preprocessor script is written in SPITBOL, which
is not acceptable for the GCC tree.
We all agree this should be done using TeXinfo preprocessing magic if
possible, or with a program in C or Ada otherwise (possibly using
the GNAT.Spitbol package).
Florian Weimer has already been working on this, but there were still
some remaining issues. Please contact him for details.
-Geert
next prev parent reply other threads:[~2001-12-02 3:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-01 3:41 guerby
2001-12-01 19:52 ` Geert Bosch [this message]
2001-12-02 3:57 ` guerby
2001-12-02 4:43 ` Joseph S. Myers
2001-12-02 7:07 ` Florian Weimer
2001-12-02 7:40 dewar
2001-12-02 9:01 ` guerby
2001-12-02 7:41 dewar
2001-12-02 7:46 dewar
2001-12-02 7:47 dewar
2001-12-02 7:51 dewar
2001-12-02 9:51 dewar
2001-12-02 9:53 dewar
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=022D9B00-E6D8-11D5-A27C-00039344BF4A@gnat.com \
--to=bosch@gnat.com \
--cc=gcc@gcc.gnu.org \
--cc=guerby@acm.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).