[comp.text.tex] Announcements: ftp, shaded boxes, epic, eepic, dvidvi

bed_gdg@SHSU.BITNET ("George D. Greenwade") (04/06/91)

Some announcements of potential interest:
1.  SHSU is now anonymous ftp-able!  The node name for connection is
    niord.shsu.edu [192.92.115.8].  The default directory in an ftp session
    is the root directory for FILESERV, and all of the packages (i.e., STY,
    AMSLaTeX_DOC, GENTLE, etc.) are in next-level subdirectories.
 
    The node niord.shsu.edu is not mailable, per se, right now (want to
    guess what we will be doing real soon?), so **PLEASE** don't try to
    send anything to user@niord.shsu.edu -- yet!  We are still SHSU.BITNET
    for mail for now.
 
2.  Regarding my post last week (maybe longer ago?) regarding shaded boxes:
    A few nice replies came in (in case I missed anyone who responded,
    thanks!) which suggested that PostScript was just about the only way to
    do this efficiently.  Some suggested looking into EEPIC, which does
    some shading between curves, etc., some suggested looking into PicTeX
    (which I will do) and one said pray real hard for something to be
    developed so that DVI files can incorporate this directly.  Short of
    the PostScript route, I guess I'm between a rock and a hard place until
    I look into EEPIC a little harder and get (actually, look harder at)
    PicTeX.
 
3.  Extending 2.  above, I did get EEPIC.  The author of EEPIC (Conrad
    Kwok) suggests that Sunil Podar's EPIC is handy to have since EEPIC is
    an extension of EPIC.  The files for both EPIC and EEPIC now are
    available on FILESERV as packages.  The description, file list, and
    instructions for retrieval of both is appended below.
 
4.  If you read the article in TUGboat (V11 #2) by Georg Denk ("An Easy Way
    Making Slides With LaTeX") and wanted the files for this, he has been
    kind enough to forward the style file, the actual text of the article,
    an example of its use, and an his \logo (for use as an example).  These
    files are, respectively, STY.ESLIDES, STY.ESLIDES_TEX,
    STY.ESLIDES-EXAMPLE_TEX, and STY.ESLIDES-LOGO-DENK.  If you want them,
    include the command
    SENDME whichever_file_it_is_you.want
    in the body of a mail message to FILESERV@SHSU.BITNET.
 
5.  Finally, Hunter Goatley was nice enough to provide me with a copy of his
    VMS port of Tom Rokicki's DVIDVI which is consistent with the new DECUS
    collection, DVIPS version 5.47, etc.  The description, file list, and
    instructions for retrieval for this package is appended below, also.
 
If anyone comes across files more recent that those in these (or any other!)
packages on FILESERV, please let me know!
 
Regards,   George
If you're not interested in the descriptions which follow on DVIDVI, EEPIC,
and EPIC (in that order), delete now!
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
                                  DVIDVI
                                  ------
The DVIDVI includes Hunter Goatley's (goathunter@wkuvx1.bitnet) February 20,
1991, port of Tom Rokicki's (rokicki@neon.stanford.edu) DVIDVI program for
VMS.  DVIDVI lets you manipulate DVI files, performing such tricks as
extracting all the even pages into a new .DVI file.  This version also
includes DUPLEX.COM, for poor-man's duplex printing.
 
The original DVIDVI created Stream_LF files under VMS; the VMS port of DVIPS
V5.47 (as well as the new DVITYPE, the latest DECUS TeX programs, etc.)
expects the file to consist of fixed-length, 512-byte records.  This version
of DVIDVI creates such files under VMS.
 
Since this package is is specifically a VMS port and probably of interest
only to VMS users, the sources necessary to rebuild this version are in a
set of 3 transfer files in VMS_SHARE format, each under the 33-block
threshold for immediate transmission.
 
You may retrieve the entire package of 3 files by MAILing the command:
SENDME DVIDVI
to FILESERV@SHSU.BITNET.  A complete distribution of this version of DVIDVI
requires all 3 files in this package, so this command is suggested. If, for
some reason, you should only need one of these files, say DVIDVI.1OF3, use
the command:
SENDME DVIDVI.1OF3
in your MAIL message to FILESERV.
 
Files in this package: (1 Block = 512 bytes)
File                        Blocks
-------------------------------------------------------------------------------
DVIDVI.1OF3, DVIDVI.2OF3        30 each
DVIDVI.3OF3                      9
 
Approximate total blocks in full DVIDVI package = 69
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
                                   EEPIC
                                   -----
The EEPIC package includes the 8 files of Conrad Kwok's EEPIC (Extensions to
EPIC and LaTeX Picture Environment (Version 1.1: Febrary 2, 1988).  EEPIC,
as an extension to both LaTeX and EPIC, tries to alleviate some of the
limitations in LaTeX, EPIC and tpic (a TeX preprocessor) by generating tpic
\special's using TeX commands instead of any preprocessor program.  At the
same time EEPIC provides compatibility with the original commands such that
when a DVI driver which understands tpic \special is not available, the
documents can still be formatted using standard LaTeX and EPIC.
 
You may retrieve the entire package of 8 files by MAILing the command:
SENDME EEPIC
to FILESERV@SHSU.BITNET.  A complete distribution of this version of EPIC
requires all 8 files in this package, so this command is suggested. If, for
some reason, you should only need one of these files, say EEPIC.README, use
the command:
SENDME EEPIC.README
in your MAIL message to FILESERV.
 
Files in this package: (1 Block = 512 bytes)
File                Blocks  Save file as:
-------------------------------------------------------------------------------
EEPIC.EEPICEMU_STY       6  EEPICEMU.STY
EEPIC.EPIC-EG3_FIG       5  EPIC-EG3.FIG
EEPIC.EPIC-EG3_TEX       6  EPIC-EG3.TEX
EEPIC.EPIC-EG4_FIG       5  EPIC-EG4.FIG
EEPIC.EPIC-EG4_TEX       6  EPIC-EG4.TEX
EEPIC.README            10  README
EEPIC.EEPIC_STY         35  EEPIC.STY
EEPIC.EEPIC_TEX         43  EEPIC.TEX
 
Approximate total blocks in full EEPIC package = 116
 
Please note that files in excess of the 33 512-byte block limit for
immediate transmittal will be queued for delivery after peak hours
(1000-1700 CST/CDT, Monday-Friday) if your request is received during
these hours.
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
                                   EPIC
                                   ----
The EPIC package includes the 8 files of Sunil Podar's EPIC (Enhancements to
the Picture Environment of LaTeX) file package (Version 1.2: July 14, 1986).
EPIC commands enhance the graphic capabilities of LaTeX and provide a
friendlier and more powerful user interface than currently existent.  The
aim of EPIC is to reduce the amount of manual calculations required to
specify the layout of objects.  EPIC commands make it possible to draw more
sophisticated pictures with lesser effort than was previously possible.
 
You may retrieve the entire package of 8 files by MAILing the command:
SENDME EPIC
to FILESERV@SHSU.BITNET.  A complete distribution of this version of EPIC
requires all 8 files in this package, so this command is suggested. If, for
some reason, you should only need one of these files, say EPIC.README, use
the command:
SENDME EPIC.README
in your MAIL message to FILESERV.
 
Files in this package: (1 Block = 512 bytes)
File                Blocks  Save file as:
-------------------------------------------------------------------------------
EPIC.MISC_STY            6  MISC.STY
EPIC.PICMAN-FIG1_TEX     2  PICMAN-FIG1.TEX
EPIC.PICMAN-FIG2_TEX     3  PICMAN-FIG2.TEX
EPIC.PICMAN-FIG3_TEX     5  PICMAN-FIG3.TEX
EPIC.PICMAN_TEX         81  PICMAN.TEX
EPIC.README              3  README
EPIC.SQRT_TEX           10  SQRT.TEX
EPIC.EPIC_STY           53  EPIC.STY
 
Approximate total blocks in full EPIC package = 163
 
Please note that files in excess of the 33 512-byte block limit for
immediate transmittal will be queued for delivery after peak hours
(1000-1700 CST/CDT, Monday-Friday) if your request is received during
these hours.