From: Luis Hernandez <newton AT math DOT gatech DOT edu>
Message-Id: <199704162119.RAA22443@math22.skiles.gatech.edu>
Subject: Compiled v2gnu manuals (82 lines)
To: djgpp AT delorie DOT com
Date: Wed, 16 Apr 1997 17:19:13 -0400 (EDT)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Precedence: bulk

Hi DJgpp'ers:

  As DJ requested to me, I'm sending to the whole list a copy of an email
that I sent to DJ yesterday about the TeXInfo manuals in dvi format. I'm
including too the answer that DJ gave me.

Original email follows:
>Hi DJ!
>
>  I compiled a lot of the v2gnu's texinfo manuals and have them in
>  dvi.gz format now. If you think that it will be usefull, I can
>  pack them all following some kind of structure (for example, I
>  can put every file into a subdir named as the respective .zip
>  file in which the original documentation comes, all under djgpp/
>  contrib/manuals, even more, I can create a .mft file to put in
>  djgpp/manifest) into a zip file and download it in your ftp's
>  incoming directory.
>  
>  I started compiling those texinfo files as a favor to a friend,
>  but after reading some emails in the djgpp list I decided to com_
>  pile some more files. Then I realized that I don't have a place 
>  where to "publish" <--> "made public" that 'work'. If you
>  like the idea, I can finish with the rest of the files (just to
>  achieve 'completeness').
>
>  By now, I only have compiled the following (huge list follows ;-)
>
(TO SAVE SOME BANDWITH I'm omitting a listing of apprx. 40 files in
 dvi.gz format)
>
>  By now, all these files need 3543Kb of storage space.

Here comes DJ's answer:

>Looks like a bit of good work.  I can't think of a good way to
>distribute these, since my server would get overloaded.  They'd
>have to go on Simtel.NET somewhere.
>
>I think that zips that expand into dvi/gcc-2721/*.dvi would be best.
>Use the directory names from the djgpp source zips (which expand to
>gnu/gcc-2721/* etc).
>
>What do you think about using the "v" letter for the zips?  Like
>bnu27v.zip?  (b=binary and s=source already; d was used by V1 for
>"docs" (info files)).
>
>I suspect that a debate about what should go in these files will
>happen on the djgpp list; best to post your query there and let
>everyone think about it.  I think a good set of files would be the
>texinfo files, Postscript, and DVI.  Maybe HTML also, if texi2html can
>be convinced to produce short enough names.
>
>Actually, if we included the info files, we could use the "d" letter
>again.
>
>I'll forward your mail back to you in case you want to resend it to
>the mailing list.

And a second DJ's reply:

>Also note: I've got a program that builds the HTML files from the
>Texinfo files for *all* GNU packages; I build
>http://www.delorie.com/gnu/docs/ with it.  I could integrate the
>texi2ps and texi2dvi steps as well, except I've never gotten around to
>building TeX for my SGI.

My original Idea was to pack all the .dvi files into *one* .zip, but to
create individual zips sounds better 'cause that way everybody will be able
to pick up the documentation that she/he wants.

Ok, we are ready to listen! ;-)

--------------------------------------------------------------------------------
Luis Hernandez. email: newton AT math DOT gatech DOT edu         29805 Georgia Tech Station
Math School, Georgia Tech.                                30332 Atlanta, GA, USA
--------------------------------------------------------------------------------
                          "I don't want to achieve inmortality through my work,
                               I want to achieve inmortality through not dying"
                                                                    Woody Allen
--------------------------------------------------------------------------------
"I'm going to live forever or die trying"
Digital Hippie
--------------------------------------------------------------------------------