|
DataMuseum.dkPresents historical artifacts from the history of: DKUUG/EUUG Conference tapes |
This is an automatic "excavation" of a thematic subset of
See our Wiki for more about DKUUG/EUUG Conference tapes Excavated with: AutoArchaeologist - Free & Open Source Software. |
top - metrics - downloadIndex: N T
Length: 1764 (0x6e4) Types: TextFile Names: »NOTE«
└─⟦52210d11f⟧ Bits:30007239 EUUGD2: TeX 3 1992-12 └─⟦af5ba6c8e⟧ »unix3.0/DVIWARE.tar.Z« └─⟦ca79c7339⟧ └─⟦this⟧ »DVIware/crt-viewers/sunview/fullscreen/NOTE«
[This file is ./DVIware/crt-viewers/sunview/fullscreen/NOTE. It is written for users of the UNIX TeX distribution. (February 1990)] NOTE: 1. The dvisun TeX previewer in this directory is intended for SUN systems running without windows. Be sure to read through the fs_dvisun.1 man page in this directory. 2. Note that this previewer prefers to work with 120 dpi fonts in pk format. If you do not have these rastered fonts, you will have to generate them in gf format via METAFONT, and convert them to pk format via the texware utility gftopk. Where you place these fonts is up to you. We recommend that the TEXFONTS environment be reserved for *.tfm font files only. 3. Next, check the file dvisun.c, line 42, where FONTAREA is defined: make certain that the path given there to the pk120 fonts matches up with the path to those fonts on your system. 4. Check the Makefile to be sure that it suits your system. Note that in spite of what the fs_dvisun.1 man page says, the program is currently set to expect a SUN2 size display and frame buffer device, not a SUN-100/150. If you have a SUN2, check to see that the file /dev/bwtwo0 exists in your /dev directory. If it does not, you will have to generate it with /dev/MAKEDEV. Similarly, if you have a SUN-100/150, check to see that the file /dev/bwone0 exists in your /dev directory. If not, generate it with /dev/MAKEDEV. 5. If you have a SUN2, type % make dvisun at your prompt (the "%" signifies your prompt). If you have a SUN100/150, type % make MFLAG="-DSUNONE" dvisun at your prompt. 6. Place the executable onto your search path (i.e., into your BINDIR).