DataMuseum.dk

top - metrics - download

    Length: 2232 (0x8b8)
    Types: TextFile
    Names: »texify.README«

└─⟦52210d11f⟧ Bits:30007239 EUUGD2: TeX 3 1992-12
    └─⟦87f627614⟧ »utils/texify.tar.Z« 
        └─⟦9880826d9⟧ 
            └─⟦this⟧ »texify.README« 

TextFile

The little program texify is a quick hack for converting various 8-bit
TeX files into a more portable 7-bit format.  It has served my needs
for a few years now, and though it has several shortcomings I have not
felt sufficient need to really go in and clean up the code and get rid
of its many irritating little quirks.  I am making it available
because others have asked for it; if I had a choice, I would spend
more time polishing it first.  (Read:  there are other things I'd
rather spend my time on).

The included files are:

texify.README	This file.
texify.c	The source code.
texify.1	The unformatted manual page, for the Unix folks.
texify.doc	The formatted manual page, for those who don't have Unix.

The program is fairly portable ANSI C, or at least I hope so.  To
compile under Unix, say something like

cc -o texify texify.c

and install the executable in your path some place.  Then, still if you
are running Unix, install texify.1 in /usr/man/man1 or wherever the
man program can get at it, perhaps run makewhatis, and you're cool.
If you are not running Unix, you have to figure these things out
yourself.  If your compiler is not ANSI compatible, you will have to
tweak the code (or get a better compiler).  In particular, all the
function declarations will have to be rewritten.

Some bugs and limitations are listed in the manual page.  Some of them
would be really simple to correct; I just haven't the time and
inclination for it.  I you wish to improve on the program, fine.  Send
me your fixes, bug reports, suggestions, and I may get around to
incorporating them, fixing them, or ignoring them.  Ready made changes
small enough for me to understand in half an hour are best.  I will
not introduce a change in the program that I don't understand; what
you do with your own copy, however, is your own business.  Just make
sure to credit yourself for any changes, as I do not want to be blamed
for other people's ``improvements'' to the code.  Please read the
copyright notice at the beginning of the code, and note the disclaimer
therein.  End of sermon.  Enjoy!

- Harald Hanche-Olsen <hanche@imf.unit.no>
  Division of Mathematical Sciences
  The Norwegian Institute of Technology
  N-7034 Trondheim, NORWAY