diff options
Diffstat (limited to 'fonts/utilities/mff-29/MANIFEST')
-rw-r--r-- | fonts/utilities/mff-29/MANIFEST | 187 |
1 files changed, 187 insertions, 0 deletions
diff --git a/fonts/utilities/mff-29/MANIFEST b/fonts/utilities/mff-29/MANIFEST new file mode 100644 index 0000000000..651f57d373 --- /dev/null +++ b/fonts/utilities/mff-29/MANIFEST @@ -0,0 +1,187 @@ + = MANIFEST = + + This manifest is rather long because it includes brief descriptions of + what the files are for. CONTENTS is a shorter directory listing. + + When archived on systems with braindead flle name conventions, such as + VMS, files with names in all-caps here may be renamed to end in ".TXT". + + + Documentation for installing mff + +README + A very short overview -- read this first... + +CONTENTS + Output of "ls -l" at some reasonable date. + +COPYING + Brief description when copies of these files may be made. + +EBCDIC + Sanity check -- BITNET gateways are known to corrupt e-mail. + +EXAMPLES + A few random examples of using mff, based on things I use it for. + +INSTALL + A brief description of how to install mff. + +MANIFEST + This list of what is in the distribution. + +NEWS + Summary of "visible" changes from previous versions. + + + Source code and makefiles + +SunPRO.mk +UNIX.mk + Makefiles [SunPRO.mk works with Sun's extended make program, which + is needed to get around Sun's extended incompatabilities]. Either link + one of these to `Makefile' or use `make -f unix.mk ...' + +config.x + C header file with site- and system-specific stuff in it. Used to + make config.h. You may need to extend it to include your own + system. + +stdc.h + Attempts to make this package compile sanely on ANSI-C and + non-ANSI-C systems -- or at least gcc and Sun's cc -- including + prototypes and void* vs. char *. A mess, sorry. + Also declares a couple of miscellaneous functions -- our system + lacks stdlib.h or whatever and GNU stddef.h conflicts with types.h. + +xstdio.h + Declarations for standard I/O -- this #include's <stdio.h> and gives + prototypes for some functions if NEEDPROTO is defined -- this is + necessary on non-ANSI-C systems using gcc. + Also declares fgetword(). + +argloop.h +assoc.h +fatal.h +fx.h +magstep.h +searchpath.h +strmisc.h + Miscellaneous C header files. + +al_file.c +al_init.c +argloop.c +assoc.c +error.c +fgetword.c +findfile.c +fx.c +magstep.c +mff.c +searchpath.c +strdup.c +stritem.c +strword.c + C source code. mff.c and searchpath.c are programs. The rest are + modules that form part of them and are packed into libargloop.a. + + + Documentation for mff itself + + I have a semi-completed TeX doc for mff, which is not in the + distribution (yet). + +numeric.t + Summary of numeric style descriptions in the style of Univers (65 is + demibold, 76 is bold oblique, etc.). + +argloop.3 +fatalf.3 +findfile.3 +mff.1 +mff.3 +searchpath.1 +shar.1 +stritem.3 +strword.3 +testfont.1 +xmalloc.3 + Manual "pages" (in troff -man format) for the programs and some of + the modules in libargloop.a. You may want to create subdirs man1 and + man3 for these. + +mff.rc + A site startup file for mff. You might like to edit this to reflect + your site. [You shouldn't set -T and -P here unless those directories + are world-writable.] This might go in /usr/local/mff or /usr/local/lib, + say, and the rc_dir in config.h altered to match. + +example.mffrc + A copy of my ~/.mffrc. On some braindead systems you may find this + renamed EXAMPLE.MFF or worse, but on those systems .mffrc files are not + used anyway. + + +testfont + Semi-useful shellscript. `testfont' is a wrapper around Knuth's + testfont.tex. + + + Example mff-based fonts + + Since these come free I hope you don't expect too much of them ... + Each font set has a brief description of the font in a file with a + name in caps named after the family (or family group) name, a mff + startup file, and METAFONT files starting with the family + abbreviation. + + These files are no longer split off into subdirectories of the + distribution, for the sake of some archivers. There are two obvious + ways to organize these files on your system: + + -- put all the .mff files in some directory /usr/local/lib/tex/mf/mff, + say, and the METAFONT files in /usr/local/lib/tex/mf/inputs; then + (assuming that the .mff file directory is put in MFFPATH) you would + create fonts with command lines like "mff -f ditko dk65s72"; or + + -- make subdirectories for each of the three font groups, and rename + the DITKO to Ditko/README, and ditko.mff to Ditko/mff.rc + and put the dk*.mf files there; then you would create fonts with + commands like "cd Ditko; mff -f dk65s72". + +FCM +fcm.mff +fcm.mf + Examples of generic driver files for three font families using the + Computer Modern character programs. + +MFLOGO +mflogo.mff +mf.mf +mfbrackets.mf +mfcaps.mf +mfcommas.mf +mfdigits.mf +mfmacros.mf +mfparams.mf +mfpunct.mf + Example font which clones Knuth's METAFONT logo (logo10 etc.). + +DITKO +ditko.mff +ditko.tex +dk.mf +dkalpha.mf +dkpunct.mf +dksym.mf + Example (incomplete) logo font. + +gray.mf + A generic light-grey "grayfont" for use with GFtoDVI. You use mff's + concept of size as the resolution of the font -- thus gray300, gray118, + whatever. See EXAMPLES. + +------------------------------------------------------------------------ +These files copyright (C) 1991, 1992 Damian Cugley +See file COPYING for details. |