From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-return-42094-listarch-gcc=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 28031 invoked by alias); 2 Dec 2001 17:51:50 -0000
Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Archive: <http://gcc.gnu.org/ml/gcc/>
List-Post: <mailto:gcc@gcc.gnu.org>
List-Help: <http://gcc.gnu.org/ml/>
Sender: gcc-owner@gcc.gnu.org
Received: (qmail 28008 invoked from network); 2 Dec 2001 17:51:48 -0000
Received: from unknown (HELO nile.gnat.com) (205.232.38.5)
  by hostedprojects.ges.redhat.com with SMTP; 2 Dec 2001 17:51:48 -0000
Received: by nile.gnat.com (Postfix, from userid 338)
	id 3C4DBF28C1; Sun,  2 Dec 2001 12:51:04 -0500 (EST)
From: dewar@gnat.com
To: dewar@gnat.com, guerby@acm.org
Subject: Re: [Ada] User Guide?
Cc: bosch@gnat.com, gcc@gcc.gnu.org
Message-Id: <20011202175104.3C4DBF28C1@nile.gnat.com>
Date: Sun, 02 Dec 2001 09:51:00 -0000
X-SW-Source: 2001-12/txt/msg00030.txt.bz2

<<My question was: is this impractical on purely commercial grounds, ie
providing support to VMS people who do not want to hear about
UNIX, so the manual must either all VMS-ish or otherwise. Or is this
technically, texinfo-technology-wise impractical? If the latter, what
are the known technical problems?
>>

I really think we have a complete solution that will work just fine here,
so let's get that together, and then discuss whether it meets our needs.
Basically we are going to try to get a texi file that works just fine
for Unix as is, and then with some preprocessing, works fine for VMS.
I think this is quite doable, and meets all requirements.