commit 11696fc746535bc19331d5ebe64d73a4ccefbe2b
parent 5ae24a666e1911031575f533e5ed2245739d7a69
Author: Kyle Milz <krwmilz@gmail.com>
Date: Sun, 29 Aug 2021 16:55:32 +0000
Garbage collect old files
Diffstat:
| D | FAQ | | | 357 | ------------------------------------------------------------------------------- |
| D | INSTALL | | | 543 | ------------------------------------------------------------------------------- |
| D | install-sh | | | 250 | ------------------------------------------------------------------------------- |
| D | mksedscript | | | 236 | ------------------------------------------------------------------------------- |
4 files changed, 0 insertions(+), 1386 deletions(-)
diff --git a/FAQ b/FAQ
@@ -1,357 +0,0 @@
-This file answers the following questions about installing xdvi:
-
- 1. Why do I get the message, ``Caution: overstrike characters may be
- incorrect'' when running netscape and xdvi simultaneously, and why
- does the screen output look so grainy?
- 2. I have font files cmr10.tfm, etc. Why can't xdvi use them?
- 3. I can't seem to set the font path correctly. Can you help me?
- 4. Whenever I run xdvi, it prints out things like:
- - mktexpk --mfmode cx --bdpi 300 --mag 'magstep(0)' --dpi 300 cmr7 '>&3'
- mktexpk: /var/cache/fonts/pk/cx/public/cm/cmr7.300pk already exists.
- Why is this?
- 5. xdvi claims to support virtual fonts, but I can't use PostScript
- virtual fonts (such as helv.vf or phvr.vf) with xdvi. Why not?
- 6. Why can't xdvi correctly display metapost files containing text?
- 7. What does the message "gs: No such file or directory" mean, and why
- does xdvi need to call ghostscript?
- 8. Why does the file selection popup look messed up when changing
- directories?
- 9. Why do I get the message "dvips: ! couldn't open output pipe"
- when I try to print, using Red Hat 8.0?
-
-as well as the following questions (dependent on some quite old versions
-of software):
-
- 10. Why do I get weird vertical color stripes when using xdvi on my S3
- Virge video card?
- 11. I am using gs 5.50 to render PostScript figures, and I find that
- sometimes characters appear on the wrong page. Why is that?
- 12. I am using gs 3.33 to render PostScript figures, but find that it
- cuts some off below or to the right of a certain point, and others
- are omitted entirely.
- 13. I am trying to display PostScript specials with -DPS_GS, but
- instead I get the message `gs: gs: Malformed ghostview color property.'
- 14. What is this "_get_wmShellWidgetClass undefined" error?
-
-Last modified: 20 June 2003
-A current copy of this file can be viewed on the WWW at the URL
-http://math.berkeley.edu/~vojta/xdvi_faq.txt
-
-----------
-
-1. Why do I get the message, ``Caution: overstrike characters may be
- incorrect'' when running netscape and xdvi simultaneously, and why
- does the screen output look so grainy?
-
-This is because your video setup has only a limited number (typically 256)
-of different colors that can be displayed at any given time, and netscape
-is using most of them. There are several ways around this problem:
-
- o Start xdvi before netscape. This should eliminate the problem for
- that copy of xdvi (only).
- o Invoke netscape via "netscape -ncols 130" This limits netscape's
- color usage to 130. Other numbers may be used as well.
- o Invoke netscape via "netscape -install" This causes netscape to run
- with its own colormap. A disadvantage of this approach is that
- netscape's colors will be bizarre when the cursor is outside netscape's
- window, and conversely all other colors on the screen will look funny
- when the cursor is in the netscape window.
-
-The screen output looks so grainy because xdvi is not able to use its
-anti-aliasing features without enough colors.
-
-----------
-
-2. I have font files cmr10.tfm, etc. Why can't xdvi use them?
-
-tfm files contain only minimal information about the characters
-in a font: just the height, width, depth, and kerning and ligature
-information. To obtain information about the shapes of the
-characters, xdvi needs pk or gf files. (pxl files also contain
-this information, but are obsolete. There are utilities to convert
-them to pk files though.)
-
-----------
-
-3. I can't seem to set the font path correctly. Can you help me?
-
-Try
- xdvi -debug 32 file.dvi
-to find out where xdvi is looking for the fonts.
-
-----------
-
-4. Whenever I run xdvi, it prints out things like:
- - mktexpk --mfmode cx --bdpi 300 --mag 'magstep(0)' --dpi 300 cmr7 '>&3'
- mktexpk: /var/cache/fonts/pk/cx/public/cm/cmr7.300pk already exists.
- Why is this?
-
-It means either that:
-
- (1) Your ls-R database is not up to date (fix this by running mktexlsr), or
- (2) Your font path is not set correctly (see #3, above).
-
-----------
-
-5. xdvi claims to support virtual fonts, but I can't use PostScript
- virtual fonts (such as helv.vf or phvr.vf) with xdvi. Why not?
-
-The short answer is to quote the man page:
-
- Virtual fonts are also supported, although xdvi does not
- have any built-in fonts to which they can refer.
-
-As further explanation, let me begin by pointing out:
-
- VIRTUAL FONTS ARE NOT FONTS.
-
-Virtual fonts are recipes for building fonts from other fonts.
-In the case of PostScript fonts, those other fonts reside on
-your printer. This is fine for dvi-to-PostScript programs
-such as dvips, but it presents a problem for xdvi since it cannot
-access your printer.
-
-There are some solutions, however.
-
-The first solution is to install gsftopk, which uses
-ghostscript to approximate the fonts. It is made for sites that
-use both xdvi and dvips, although if you just use xdvi it should
-be useful, too.
-
-Another solution is to get these fonts pre-made in common sizes.
-These were made by a program called gsrenderfont (part of the Gnu
-font utilities).
-
-These are all available via anonymous ftp:
-
-gsftopk from math.berkeley.edu:pub/TeX/gsftopk.tar.Z
-pre-made fonts from ftp.cs.umb.edu:pub/tex/psfonts.tar
-gsrenderfont from prep.ai.mit.edu:pub/gnu/fontutils-0.6.tar.gz
-
-----------
-
-6. Why can't xdvi correctly display metapost files containing text?
-
-The problem is that the PS files created by MP are (normally) not
-self-contained. xdvi delegates the display of PS files to
-ghostscript, which fails to handle those files.
-
-A solution is to instruct MP to create true EPS files, by including
- prologues:=2;
-at the top of the document. If you have the CM postscript fonts
-installed so that ghostscript can find them, you can continue to use
-the CM fonts, otherwise you'll have to switch to Times or such for the
-illustrations.
-
-Switching the fonts can be done setting 'defaultfont' to something
-like "ptmr8r" (for Times). For the TeX material in 'btex .. etex'
-blocks, it is best to set up the fonts once in a 'verbatimtex .. etex'
-block. (And same for LaTeX of course.)
-
-This answer courtesy of Olaf Weber.
-
-----------
-
-7. What does the message "gs: No such file or directory" mean, and why
- does xdvi need to call ghostscript?
-
-The message "gs: No such file or directory" means that xdvi needs to call
-ghostscript, but does not find it on your system. Ghostscript is a program
-used for rendering PostScript. It is needed by xdvi (1) for displaying
-PostScript specials in documents, and (2) for rendering PostScript fonts
-occurring in documents. In the latter case, xdvi calls a script (usually
-named mktexpk) which in turn calls the program gsftopk to render the font
-in a form usable by xdvi.
-
-----------
-
-8. Why does the file selection popup look messed up when changing
- directories?
-
-This is a bug with XFree86 version 4.0.1a (and possibly other versions).
-Upgrading to version 4.0.3 (or newer) should fix the problem.
-
-----------
-
-9. Why do I get the message "dvips: ! couldn't open output pipe"
- when I try to print, using Red Hat 8.0?
-
-When trying to print a file, the log window shows the following output:
-
- This is dvips(k) 5.86 Copyright 1999 Radical Eye
- Software (www.radicaleye.com)
- ' TeX output 2003.04.08:1919' -> !lpr
- dvips: ! couldn't open output pipe
-
-This is a known bug in (RedHat's customized version of) dvips' `secure mode',
-forbidding dvips to open pipes for printing; see also the bug report:
-
- https://sourceforge.net/tracker/index.php?func=detail&aid=717663&group_id=23164&atid=377580
-
-and the discussion on the tetex mailing list:
-
- http://www.mail-archive.com/tetex@informatik.uni-hannover.de/msg01782.html
-
-A possible workaround is to set the xdvi command-line option `-dvipspath'
-or the `.dvipsPath' X resource to a wrapper script that invokes dvips in
-a way that avoids the problem. An example for such a script (in Perl)
-is shown here:
-
---- begin script ---
-#!/usr/bin/perl -w
-#
-# Wrapper for xdvi to launch dvips and avoid its secure feature that disallows
-# piping to lpr (dvips 5.92b / RH 8.0; 4/2003). Specify with -dvipspath option
-# (or .dvipsPath X11 resource) in xdvi. Written by S. Ulrich and P. Vojta.
-
-my @dvips_args = ("dvips");
-my $lpr_cmd;
-
-# Extract lpr command from the dvips args given in implicit pipe, if any
-foreach (@ARGV) {
- if (/^-o[!\|](.*)/) {
- $lpr_cmd = '|' . $1;
- } else {
- push (@dvips_args, $_);
- }
-}
-
-# Construct explicit pipe with given lpr command
-if (defined $lpr_cmd) {
- open(STDOUT, $lpr_cmd)
- or die "Couldn't open output pipe $lpr_cmd: $!";
-}
-
-# Exec over to dvips
-exec @dvips_args
- or die "Couldn't exec dvips: $!";
---- end script ---
-
-----------
-
-10. Why do I get weird vertical color stripes when using xdvi on my
- S3 Virge video card?
-
-This is a bug in the XF86_S3V X server. It has been reported to XFree86.
-The response from them is that the XF86_S3V server is being phased out
-and that users should use the XF86_SVGA server instead (which also, as of
-XFree86 3.3.3, supports the S3 Virge chipset).
-
-----------
-
-11. I am using gs 5.50 to render PostScript figures, and I find that
- sometimes characters appear on the wrong page. Why is that?
-
-This is a bug in ghostscript 5.50. The following patch will fix it:
-
-*** gdevx.c.orig Fri Jul 17 07:31:27 1998
---- gdevx.c Sat Oct 17 23:42:50 1998
-***************
-*** 59,65 ****
- ((gx_device_X *)(dev))->up_area = 0,\
- ((gx_device_X *)(dev))->up_count = 0
- #define update_flush(dev)\
-! if ( ((gx_device_X *)(dev))->up_area != 0 ) update_do_flush(dev)
- private void update_do_flush(P1(gx_device *));
-
- #define flush_text(dev)\
---- 59,66 ----
- ((gx_device_X *)(dev))->up_area = 0,\
- ((gx_device_X *)(dev))->up_count = 0
- #define update_flush(dev)\
-! if ( ((gx_device_X *)(dev))->up_area != 0 || IN_TEXT((gx_device_X *)(dev)) )\
-! update_do_flush(dev)
- private void update_do_flush(P1(gx_device *));
-
- #define flush_text(dev)\
-
-----------
-
-12. I am using gs 3.33 to render PostScript figures, but find that it
- cuts some off below or to the right of a certain point, and others
- are omitted entirely.
-
-You should apply the following patch. This will also fix similar errors
-with ghostview. This patch supersedes a previous patch I have suggested
-to some people.
-
-*** gdevxini.c.orig Sun Nov 6 13:46:42 1994
---- gdevxini.c Mon Jun 5 15:40:18 1995
-***************
-*** 319,344 ****
-
- /* The following sets the imageable area according to the */
- /* bounding box and margins sent by ghostview. */
-! { float m[4];
-! m[0] = (llx - left_margin) / 72.0; /* left */
-! m[1] = (lly - bottom_margin) / 72.0; /* bottom */
-! m[2] = xdev->width / xdev->x_pixels_per_inch -
-! (urx + right_margin) / 72.0; /* right */
-! m[3] = xdev->height / xdev->y_pixels_per_inch -
-! (ury + top_margin) / 72.0; /* top */
-!
-! /******
-! ****** For reasons I don't understand,
-! ****** we have to set the margins to zero here
-! ****** in order for Ghostview to do landscape display right.
-! ******/
-! #if 0
-! m[0] = m[1] = m[2] = m[3] = 0;
-! #endif
-!
-! gx_device_set_margins((gx_device *)xdev, m, false);
-! }
-!
- } else if (xdev->pwin == (Window)None) {
- eprintf("gs: Cannot get ghostview property.\n");
- exit(1);
---- 319,329 ----
-
- /* The following sets the imageable area according to the */
- /* bounding box and margins sent by ghostview. */
-! xdev->ImagingBBox[0] = llx - left_margin;
-! xdev->ImagingBBox[1] = lly - bottom_margin;
-! xdev->ImagingBBox[2] = urx + right_margin;
-! xdev->ImagingBBox[3] = ury + top_margin;
-! xdev->ImagingBBox_set = true;
- } else if (xdev->pwin == (Window)None) {
- eprintf("gs: Cannot get ghostview property.\n");
- exit(1);
-
-----------
-
-13. I am trying to display PostScript specials with -DPS_GS, but
- instead I get the message `gs: gs: Malformed ghostview color property.'
-
-xdvi needs at least version 2.6.2 of ghostscript. It will also run with
-ghostscript 2.6.1, provided you have applied fixes 1-4. This particular
-error message means that you are running gs 2.6.1 without fixes 1-4.
-Probably you should get a newer version of ghostscript.
-
-----------
-
-14. What is this "_get_wmShellWidgetClass undefined" error?
-
- In SunOS 4.1.2 Sun fixed a shared-library bug in ld which conflicts
-with the way X builds the shared Xmu library, causing these symbols, notably,
-to be undefined when building some X11 clients on SunOS 4.1.[23]:
- _get_wmShellWidgetClass
- _get_applicationShellWidgetClass
-Compiling "-Bstatic -lXmu -Bdynamic" is overkill; be sure to set
-OSTeenyVersion correctly in the config/sun.cf file and rebuild X11R5.
-
-To solve the problem if you are using OpenWindows 3.0 (X11R4-based Xt), please
-contact your local Sun office and request the following patches:
-
-Patch i.d. Description
-100512-02 4.1.x OpenWindows 3.0 libXt Jumbo patch
-100573-04 OpenWindows 3.0: xstdcmap fails to set XStandardColomap for
- 24-bit machines [this also fixes bug 1087332, "With patched
- ld and libc, customer is getting undefined symbols"]
-
-[Greg Earle, earle@Sun.COM; 7/92]
-
-A source patch for use with the X11R4 libraries was developed by Conrad
-Kimball (cek@sdc.boeing.com); it retrofits into R4 some fixes made in R5 to
-get around this problem. The patch is on ftp.x.org in [1/93]
- contrib/X11R4_sunos4.1.2_patch_version3.Z
diff --git a/INSTALL b/INSTALL
@@ -1,543 +0,0 @@
-INSTALLATION INSTRUCTIONS
-
- xdvi now uses a `configure' shell script to guess correct values for
-various system-dependent variables used during compilation. The mechanism
-it uses to implement those values depends on whether imake is being used
-or not, but in both cases it creates a file `config.h' that is included
-by the C source files. It also creates a shell script `config.status' that
-you can run in the future to recreate the current configuration, a file
-`config.cache' that saves the results of its tests to speed up
-reconfiguring, and a file `config.log' containing compiler output
-(useful mainly for debugging `configure').
-
- The file `configure.in' is used to create `configure' by a program
-called `autoconf'. You only need `configure.in' if you want to change
-it or regenerate `configure' using a newer version of `autoconf'. If
-so, see the file `xautocnf.txt' for details on some custom modifications
-to autoconf.
-
- xdvi can be installed either with the standard X tool `imake,' or with
-just plain `make.' Follow the directions in the appropriate section of
-this file.
-
- EXCEPTION: Users of using teTeX should go directly to the section
-`COMPILING FOR USE WITH TETEX' below.
-
-
-COMPILING WITH MAKE
-
-To compile and install with make, do the following:
-
- 1. `cd' to the directory containing the package's source code and type:
-
- ./configure --datadir=[your texmf tree]
-
- to configure the package for your system. If you're using `csh' on
- an old version of System V, you might need to type
-
- sh ./configure --datadir=[your texmf tree]
-
- instead to prevent `csh' from trying to execute `configure' itself.
-
- You may want to run `configure' with additional arguments to indicate
- where it is to be installed, where the X Window System libraries
- and include files are, and what program features are to be enabled
- or disabled. See the section `CONFIGURE SCRIPT OPTIONS' for
- details.
-
- While running, `configure' prints some messages telling which
- features it is checking for. When done, it creates a Makefile
- and a file config.h containing the options it has determined.
-
- 2. Compile xdvi:
-
- make
-
- 3. Try out xdvi.
-
- If the settings in Step 1 are incorrect, then you can use the
- corresponding environment variables to quickly try out different
- values. Then go back to Step 1.
-
- 4. Install by typing:
-
- make install
-
- 5. If you are compiling for several architectures, type
-
- make archclean
-
- and repeat the above steps on each different machine.
-
- 6. To enable xdvi as a helper application from within the browser, follow
- the instructions given in the man page for xdvizilla.
-
-
-COMPILING WITH IMAKE
-
-This will probably not work with X11R4 and earlier.
-
-To compile and install with imake, do the following:
-
- 1. `cd' to the directory containing the package's source code.
-
- 2. Edit the Imakefile according to the directions contained in that file.
-
- 3. Create the Makefile by typing:
-
- xmkmf
-
- 4. Compile xdvi:
-
- make depend
- make
-
- 5. Try out xdvi.
-
- If the settings in Step 2 are incorrect, then you can use the
- corresponding environment variables to quickly try out different
- values. Then go back to Step 2.
-
- 6. Install by typing:
-
- make install install.man
-
- 7. If you are compiling for several architectures, type
-
- make archclean
-
- and repeat the above steps on each different machine.
-
- 8. To enable xdvi as a helper application from within the browser, follow
- the instructions given in the man page for xdvizilla.
-
- 9. If you have made any changes to config.xdvi (this is rare), then you
- should install it manually in the dvips/config subdirectory of an
- appropriate texmf tree. Remember to run mktexlsr again.
-
-CONFIGURE SCRIPT OPTIONS
-
- The `configure' script is similar to others created by GNU autoconf,
- except that it has been modified to support the different needs of
- X applications. It recognizes the following options to control how
- it operates:
-
- --help
- Print a summary of the options to `configure', and exit.
-
- --x-top=DIR
- Look for X include files in directory DIR/include and for X libraries
- in directory DIR/lib. This is a convenient replacement for
- the options --x-includes and --x-libraries.
-
- --aux-top=DIR
- Look for additional X include files in DIR/include and library files
- in DIR/lib. This is useful, for example, if a locally installed
- toolkit is being used.
-
- --prefix=DIR
- This option determines default values for the --bindir and --mandir
- options. The default value is the directory specified in --x-top
- (if one was given); otherwise /usr/local.
-
- --bindir=DIR
- Install the xdvi executable in DIR. By default, it will be placed
- in the directory PREFIX/bin, where PREFIX is the value of the
- --prefix option.
-
- --mandir=DIR
- Install the xdvi manual page in DIR/man1. By default, it will be
- placed in the directory PREFIX/man/man1, where PREFIX is the value
- of the --prefix option.
-
- --datadir=DIR
- Install the file config.xdvi in DIR/dvips/config. This should be set
- whenever configuring xdvi. Normally DIR will be the texmf tree that is
- to contain most of the files that TeX uses; e.g.,
- /usr/local/texlive/2013/texmf-dist . If TeX is already installed,
- then --datadir="`kpsewhich -var-value TEXMFMAIN`" should work.
-
- --x-includes=DIR
- Look for X include files in directory DIR.
-
- --x-libraries=DIR
- Look for X libraries in directory DIR.
-
- --with-x-toolkit=PKG
- --without-x-toolkit
- Use the PKG toolkit for xdvi. PKG may be `xaw' (use the Xaw
- toolkit), `xaw3d' (use the Xaw3d toolkit as a drop-in replacement for
- Xaw), `motif' (use the Motif toolkit), or `no' (use raw X calls).
- By default, xdvi will use the Xaw toolkit. `--without-x-toolkit'
- is the same as `--with-x-toolkit=no'.
-
- --enable-freetype[=DIR]
- --disable-freetype
- Use the FreeType library in xdvi. This allows xdvi to use scalable
- PostScript fonts instead of font files that must be created for each
- size at which the font is to be used. (This is enabled by default.)
-
- --disable-grey
- Disable greyscale anti-aliasing for displaying shrunken bitmaps.
- (This is enabled by default.)
-
- --disable-color
- Disable support for dvips-style color specials. (This is enabled
- by default.)
-
- --disable-buttons
- Disable the placement of radio buttons on the right side of the
- window for commonly used commands. This option is automatically
- disabled when compiling without a toolkit.
-
- --disable-make-pk
- If xdvi is compiled without disabling this option, it will use a
- script called `mktexpk' or `MakeTeXPK' to call Metafont to render
- a font at the desired size if that size is not already available.
- This option turns off this feature.
-
- --enable-make-pk=PATH
- Specifies PATH as the name of the script for dynamically creating
- font pixel files. This is the default value of the XDVIMAKEPK
- environment variable; see the discussion of XDVIMAKEPK in the manual
- page for more information.
-
- --enable-old-make-pk
- --enable-old-make-pk=PATH
- Use an old `MakeTeXPK' script instead of `mktexpk' to dynamically
- create font pixel files. If given, PATH is as in `--enable-make-pk';
- if not given, the default is `MakeTeXPK.' This option supersedes
- the `--enable-make-pk' option.
-
- --enable-gf
- Enable support for Metafont `gf' font pixel files. (The `pk' format
- for font pixel files is always enabled.)
-
- --enable-ps-gs
- --enable-ps-gs=PATH
- Enable use of Ghostscript<TM> to render PostScript<TM> specials.
- Your system must have Ghostscript installed for this to work.
- Versions earlier than 2.6.1 have not been tested with xdvi. The
- PATH is the path of the ghostscript executable; "gs" by default.
- This option can be used in combination with either of the next two
- `--enable-ps-' options. If one of them is enabled, then they take
- precedence over Ghostscript.
-
- --enable-ps-dps
- Enable use of Display PostScript<TM> to render PostScript specials.
- Your system must have DPS for this to work.
-
- --enable-ps-news
- Enable use of NeWS server to display PostScript specials. Your
- system must have the NeWS include files and libraries for this to
- compile; the xdvi binary can be run with either a standard X server
- or the NeWS server, but in the former case the code generated by
- PS_NEWS will have no effect. NOTE: This option refers only to
- OpenWindows versions 3.1 (possibly 3.2) and earlier (running under
- SunOS 4.x). If you are using Solaris 2, then you should use PS_DPS
- instead.
-
- --enable-config-file=PATHLIST
- Enable use of a configuration file in xdvi. The PATHLIST should be
- a colon-separated list of directories to be searched for a
- configuration file named `texmf.cnf.'
-
- --enable-self-auto
- --enable-self-auto=PATHLIST
- Enable configuration files; also enable special symbols SELFAUTODIR
- and SELFAUTOPARENT in the config file. This option also selects for
- the use of config files; if no PATHLIST is given, the value
- ".:$SELFAUTOLOC:$SELFAUTODIR:$SELFAUTOPARENT
- :$SELFAUTODIR/share/texmf/web2c:$SELFAUTOPARENT/share/texmf/web2c
- :$SELFAUTODIR/texmf/web2c:$SELFAUTOPARENT/texmf/web2c
- :$TETEXDIR:$TEXMF/web2c" (without the line breaks) is used.
-
- --enable-extra-app-defaults
- --enable-extra-app-defaults=PATHLIST
- Selects `--enable-self-auto' (with PATHLIST, if given); in addition,
- it causes xdvi to look for a second app-defaults file, either in the
- root directory of the texmf tree, or in the xdvi or web2c
- subdirectories. This option is primarily intended for copies of xdvi
- that are to be distributed with precompiled TeX distributions such as
- teTeX. This option is not available when compiling without a toolkit.
-
- --enable-dosnames
- Check also for pk or gf files with names like dpi329/cmr10.pk
- (instead of cmr10.329pk).
-
- --enable-a4
- Set the default paper size to `a4' instead of 8.5 x 11 inches.
- Also change the default unit from inches to centimeters.
-
- --enable-texxet
- Enable support for dvi op-codes 250 and 251 (used for typesetting
- right-to-left languages).
-
- --with-mfmode=MODE:DPI
- Set the default value for the `-mfmode' option to `MODE:DPI'.
- (This is the Metafont mode used when creating fonts.) If neither this
- option nor `--without-mfmode' is selected, then the default value
- is `cx:300'.
-
- --without-mfmode
- Indicate that the `-mfmode' option has no default value.
-
- --with-tetex
- --with-tetex=PATHLIST
- This causes --enable-ps-gs, --enable-dosnames, and
- --enable-extra-app-defaults to be set by default (their values can be
- overridden explicitly). If a PATHLIST is given, it is passed to
- the --enable-extra-app-defaults argument.
-
- --with-default-texmf-path=PATH
- Set the default value of the TEXMF environment variable.
-
- --with-default-font-path=PATH
- Set the default value of the XDVIFONTS environment variable.
-
- --with-default-vf-path=PATH
- Set the default value of the VFFONTS environment variable.
-
- --with-default-header-path=PATH
- Set the default value of the XDVIHEADERS environment variable.
-
- --with-default-fig-path=PATH
- Set the default value of the XDVIPICTS environment variable.
-
- --with-default-source-path=PATH
- Set the default value of the XDVISOURCES environment variable.
-
- --with-default-dvips-cf-path=PATH
- Set the default value of the XDVITYPE1CONFIG environment variable.
-
- --with-default-fontmap-path=PATH
- Set the default value of the XDVIFONTMAPS environment variable.
-
- --with-default-enc-path=PATH
- Set the default value of the XDVIENCS environment variable.
-
- --with-default-type1-path=PATH
- Set the default value of the XDVIT1FONTS environment variable.
-
- --with-default-gs-lib-path=PATH
- Set the default value of the XDVI_GS_LIB environment variable.
-
- --with-default-dvips-path=CMD
- Set the default value of the dvipsPath resource, which gives the
- command to use for printing (not applicable if compiling without the
- X Toolkit).
-
-
-ADDITIONAL OPTIONS
-
- Some additional rarely-used options may also be set in the `configure'
- script. To do so, set the `CPPFLAGS' variable explicitly. This can
- be done as in the following examples:
-
- If using make and using the C-shell (/bin/csh, /bin/tcsh, etc.):
-
- env CPPFLAGS='-DALTFONT="ptmr8r"' ./configure
-
- If using make and using a Bourne-like shell (/bin/sh, /bin/bash,
- /bin/ksh, etc.):
-
- CPPFLAGS='-DALTFONT="ptmr8r"' ./configure
-
- If using imake: See the instructions for setting DEFS in the Imakefile.
-
- (Of course, options such as --prefix may be supplied to `configure'
- as well.)
-
- The following options are supported in CPPFLAGS:
-
- Option Flag Explanation
- ----------- -----------
-
- ALTFONT Default font to use if the font named in the dvi file
- cannot be found. Can be set to NULL. By default,
- it is "cmr10".
- BDPI Default number of pixels per inch to use. It is better
- to set this value by setting the default metafont mode
- instead.
- DEFAULT_FONT_SIZES Colon-separated list of font sizes to look for if the exact size cannot be found, and if automatic
- generation of pixel files fails. See the description
- of the XDVISIZES environment variable in the manual
- page for more details.
- SHRINK Default value for the -s option (shrink factor).
- If not specified, the default will be 3.
- XDVIFONTS_ONLY Never check the TEXFONTS environment variable.
- Normally xdvi checks TEXFONTS if the XDVIFONTS variable
- is not set. This option is recommended if the version
- of TeX in use requires that the TEXFONTS variable be
- set. See the relevant paragraph in xdvi-man.sed for
- more details. This option turns off that paragraph.
- MKPK_REDIRECT Enables use of the `%r' specifier for MakeTeXPK scripts
- that support sending the file name to a numbered file
- descriptor instead of standard output. This implies
- -DMAKEPK.
- NOQUERY Set this if you have trouble compiling the definition
- of drawingWidgetClass.
- TICKTMP Directory for temporary files created by PostScript
- specials that call for the output of a command (e.g.,
- compressed .eps files). Default is "/tmp".
- TICKCACHESIZE Maximum number of such files to be stored at a time
- (this is dynamically increased if more than this number
- occur on a single page). Default is 3.
-
-
-SETTING PATHS
-
- Read the ENVIRONMENT section of xdvi-man.sed to determine the correct
- default values for the TEXMF and XDVIFONTS environment variables.
- These should be specified as arguments to `./configure' (which can
- be set in the Imakefile, if you are going that route).
- If your site uses virtual fonts, do the same thing with the
- VFFONTS variable. Note that support of virtual fonts in xdvi
- does not include support of built-in PostScript<tm> fonts.
- Usually you will want to use the same font files as your printer;
- given a choice, however, it has been suggested that write-white
- fonts look better.
-
- If you are compiling with PostScript specials enabled, then
- you also need to set default values for the XDVIPICTS and
- XDVIHEADERS variables. These should contain colon-separated
- lists of directories. The XDVIPICTS variable gives the list
- of directories to search for PostScript figures; typically
- this is the same as the default input directory used by TeX.
- The XDVIHEADERS variable gives the default list of directories
- to search for PostScript headers. If you also install dvips,
- then it is recommended that XDVIPICTS and XDVIHEADERS be set to the
- same values as FIGPATH and HEADERPATH in the Makefile for dvips.
-
- If you are compiling with a configuration file, then the paths
- described above are less important, since they can be set in the
- configuration file.
-
-
-NOTES FOR SPECIFIC OPERATING SYSTEMS
-
- This section is probably not necessary, and will be deleted eventually.
- If you find that part of it is needed, please let me know by sending
- e-mail to vojta@math.berkeley.edu.
-
- SGI/IRIX 4: You can substantially reduce the size of the xdvi binary
- by linking with -lX11_s instead of -lX11 and -lXt_s instead of -lXt.
- This requires some hacking in the Makefile.
-
- SGI/IRIX 5.1: If you are not using imake, add
-
- -cckr -float -KPIC -G 0 -Wf,-XNh2000
-
- to CFLAGS when configuring (by treating CFLAGS similarly to
- CPPFLAGS, as above).
-
- Sun/Solaris 2.x: If you are using the X11R6 server (as opposed to the
- OpenWindows server) and are running Solaris 2.4 or earlier, then
- a bug in the threads library may cause xdvi to fail to work
- (it won't respond to keystrokes or may not display the page).
- If you experience this problem, edit config.h after running
- `configure,' and undefine HAVE_STREAMS.
- Or, better yet, try to get the appropriate patch from Sun, since
- you are probably having other problems with X, too.
-
- IBM RS6000: Some of the libraries are in non-obvious places:
-
- libXmu /usr/lpp/X11/Xamples/lib/Xmu/libXmu.a
- libXaw /usr/lpp/X11/Xamples/lib/Xaw/libXaw.a
-
- These should be moved to /usr/lib or some more reasonable place
- (or use symlinks), and ditto for the include files, which are
- initially placed in /usr/lpp/X11/Xamples/include.
-
-
-COMPILING FOR USE WITH TETEX
-
- If you are replacing the version of xdvi that comes with the teTeX
- distribution of TeX (these instructions work with Versions 0.4 and 1.0),
- you need to:
-
- 1. Determine where the xdvi binary and manual page are to go. If you
- have the `locate' command installed on your system, you can type
- `locate xdvi' to find them.
-
- 2. Run the following command to configure this version of xdvi.
- The --bindir and --mandir arguments should be the directories
- determined in Step 1. Note, however, that the --mandir directory
- should end in `/man', not in `/man/man1'.
-
- Also, if you found that xdvi and xdvi.1 were located in /usr/bin
- and /usr/man/man1, respectively, then the `--bindir' and `--mandir'
- arguments should be omitted. In that case `configure' will put them in
- /usr/local/bin and /usr/local/man(/man1) by default, and this version
- of xdvi will supersede the system version because presumably
- /usr/local/bin and /usr/local/man will be searched before /usr/bin
- and /usr/man. This paragraph applies, for example, to the teTeX that
- comes with Debian Linux systems. (As a general rule, locally installed
- programs should go into /usr/local.)
-
- ./configure --with-tetex --bindir=/usr/local/teTeX/bin/i386-linux \
- --mandir=/usr/local/teTeX/man
-
- In the above example, the `--bindir' and `--mandir' arguments should
- be correct for a locally installed version of teTeX.
-
- If you are using teTeX version 0.4, you should also include
- --enable-old-make-pk in the above arguments.
-
- You may also, of course, use other `configure' options in addition.
-
- 3. Locate the file texmf.cnf and add the following lines. They must go
- before any of these symbols are defined without the .XDvi suffix:
-
- PKFONTS.XDvi = .:$TEXMF/%s:$VARTEXFONTS/pk/{%m,modeless}//
- VFFONTS.XDvi = .:$TEXMF/%s
- PSHEADERS.XDvi = .:$TEXMF/%q{dvips,fonts/type1}//
- TEXPICTS.XDvi = .:$TEXMF/%q{dvips,tex}//
-
- In teTeX 0.4, use $TEXMFS instead of $TEXMF and VARFONTS instead of
- VARTEXFONTS in the above lines.
-
- You may also define MFMODE, PIXELSPERINCH, SHRINKFACTOR, and PAPER in
- texmf.cnf. For example, if your $TEXMF/xdvi/XDvi file contains
-
- XDvi*mfmode: ljfour
- XDvi*pixelsPerInch: 600
- XDvi*shrinkFactor: 4
- XDvi*paper: letter
-
- then the following lines can go into texmf.cnf:
-
- MFMODE = ljfour
- PIXELSPERINCH = 600
- SHRINKFACTOR = 4
- PAPER = letter
-
- You can also put lines such as:
-
- SHRINKBUTTON1 = 1
- SHRINKBUTTON2 = 3
- SHRINKBUTTON3 = 4
- SHRINKBUTTON4 = 6
-
- into texmf.cnf to change the labels on the buttons. You will probably
- need to be root to edit texmf.cnf.
-
- 4. Type "make" and see if it produces any error messages. If it does,
- study the documentation above, make whatever changes to the Makefile
- seem appropriate, then "make clean" and "make" again.
-
- 5. Before installing xdvi, you may remove `xdvi.bin' from the binary
- directory. Or, if you wish to still be able to run the version of
- xdvik that comes with teTeX, rename `xdvi' to `xdvik' and leave
- `xdvi.bin' alone. Omit this step if you omitted the `--bindir'
- and `--mandir' arguments in Step 2. In that case, you will be able
- to run the old xdvi by using its full path: `/usr/bin/xdvi ...'.
-
- 6. Install xdvi and its man page by typing:
-
- make install
-
- You will probably need to do this as root.
-
- 7. To enable xdvi as a helper application from within the browser, follow
- the instructions given in the man page for xdvizilla.
diff --git a/install-sh b/install-sh
@@ -1,250 +0,0 @@
-#! /bin/sh
-#
-# install - install a program, script, or datafile
-# This comes from X11R5 (mit/util/scripts/install.sh).
-#
-# Copyright 1991 by the Massachusetts Institute of Technology
-#
-# Permission to use, copy, modify, distribute, and sell this software and its
-# documentation for any purpose is hereby granted without fee, provided that
-# the above copyright notice appear in all copies and that both that
-# copyright notice and this permission notice appear in supporting
-# documentation, and that the name of M.I.T. not be used in advertising or
-# publicity pertaining to distribution of the software without specific,
-# written prior permission. M.I.T. makes no representations about the
-# suitability of this software for any purpose. It is provided "as is"
-# without express or implied warranty.
-#
-# Calling this script install-sh is preferred over install.sh, to prevent
-# `make' implicit rules from creating a file called install from it
-# when there is no Makefile.
-#
-# This script is compatible with the BSD install script, but was written
-# from scratch. It can only install one file at a time, a restriction
-# shared with many OS's install programs.
-
-
-# set DOITPROG to echo to test this script
-
-# Don't use :- since 4.3BSD and earlier shells don't like it.
-doit="${DOITPROG-}"
-
-
-# put in absolute paths if you don't have them in your path; or use env. vars.
-
-mvprog="${MVPROG-mv}"
-cpprog="${CPPROG-cp}"
-chmodprog="${CHMODPROG-chmod}"
-chownprog="${CHOWNPROG-chown}"
-chgrpprog="${CHGRPPROG-chgrp}"
-stripprog="${STRIPPROG-strip}"
-rmprog="${RMPROG-rm}"
-mkdirprog="${MKDIRPROG-mkdir}"
-
-transformbasename=""
-transform_arg=""
-instcmd="$mvprog"
-chmodcmd="$chmodprog 0755"
-chowncmd=""
-chgrpcmd=""
-stripcmd=""
-rmcmd="$rmprog -f"
-mvcmd="$mvprog"
-src=""
-dst=""
-dir_arg=""
-
-while [ x"$1" != x ]; do
- case $1 in
- -c) instcmd="$cpprog"
- shift
- continue;;
-
- -d) dir_arg=true
- shift
- continue;;
-
- -m) chmodcmd="$chmodprog $2"
- shift
- shift
- continue;;
-
- -o) chowncmd="$chownprog $2"
- shift
- shift
- continue;;
-
- -g) chgrpcmd="$chgrpprog $2"
- shift
- shift
- continue;;
-
- -s) stripcmd="$stripprog"
- shift
- continue;;
-
- -t=*) transformarg=`echo $1 | sed 's/-t=//'`
- shift
- continue;;
-
- -b=*) transformbasename=`echo $1 | sed 's/-b=//'`
- shift
- continue;;
-
- *) if [ x"$src" = x ]
- then
- src=$1
- else
- # this colon is to work around a 386BSD /bin/sh bug
- :
- dst=$1
- fi
- shift
- continue;;
- esac
-done
-
-if [ x"$src" = x ]
-then
- echo "install: no input file specified"
- exit 1
-else
- true
-fi
-
-if [ x"$dir_arg" != x ]; then
- dst=$src
- src=""
-
- if [ -d $dst ]; then
- instcmd=:
- else
- instcmd=mkdir
- fi
-else
-
-# Waiting for this to be detected by the "$instcmd $src $dsttmp" command
-# might cause directories to be created, which would be especially bad
-# if $src (and thus $dsttmp) contains '*'.
-
- if [ -f $src -o -d $src ]
- then
- true
- else
- echo "install: $src does not exist"
- exit 1
- fi
-
- if [ x"$dst" = x ]
- then
- echo "install: no destination specified"
- exit 1
- else
- true
- fi
-
-# If destination is a directory, append the input filename; if your system
-# does not like double slashes in filenames, you may need to add some logic
-
- if [ -d $dst ]
- then
- dst="$dst"/`basename $src`
- else
- true
- fi
-fi
-
-## this sed command emulates the dirname command
-dstdir=`echo $dst | sed -e 's,[^/]*$,,;s,/$,,;s,^$,.,'`
-
-# Make sure that the destination directory exists.
-# this part is taken from Noah Friedman's mkinstalldirs script
-
-# Skip lots of stat calls in the usual case.
-if [ ! -d "$dstdir" ]; then
-defaultIFS='
-'
-IFS="${IFS-${defaultIFS}}"
-
-oIFS="${IFS}"
-# Some sh's can't handle IFS=/ for some reason.
-IFS='%'
-set - `echo ${dstdir} | sed -e 's@/@%@g' -e 's@^%@/@'`
-IFS="${oIFS}"
-
-pathcomp=''
-
-while [ $# -ne 0 ] ; do
- pathcomp="${pathcomp}${1}"
- shift
-
- if [ ! -d "${pathcomp}" ] ;
- then
- $mkdirprog "${pathcomp}"
- else
- true
- fi
-
- pathcomp="${pathcomp}/"
-done
-fi
-
-if [ x"$dir_arg" != x ]
-then
- $doit $instcmd $dst &&
-
- if [ x"$chowncmd" != x ]; then $doit $chowncmd $dst; else true ; fi &&
- if [ x"$chgrpcmd" != x ]; then $doit $chgrpcmd $dst; else true ; fi &&
- if [ x"$stripcmd" != x ]; then $doit $stripcmd $dst; else true ; fi &&
- if [ x"$chmodcmd" != x ]; then $doit $chmodcmd $dst; else true ; fi
-else
-
-# If we're going to rename the final executable, determine the name now.
-
- if [ x"$transformarg" = x ]
- then
- dstfile=`basename $dst`
- else
- dstfile=`basename $dst $transformbasename |
- sed $transformarg`$transformbasename
- fi
-
-# don't allow the sed command to completely eliminate the filename
-
- if [ x"$dstfile" = x ]
- then
- dstfile=`basename $dst`
- else
- true
- fi
-
-# Make a temp file name in the proper directory.
-
- dsttmp=$dstdir/#inst.$$#
-
-# Move or copy the file name to the temp name
-
- $doit $instcmd $src $dsttmp &&
-
- trap "rm -f ${dsttmp}" 0 &&
-
-# and set any options; do chmod last to preserve setuid bits
-
-# If any of these fail, we abort the whole thing. If we want to
-# ignore errors from any of these, just make sure not to ignore
-# errors from the above "$doit $instcmd $src $dsttmp" command.
-
- if [ x"$chowncmd" != x ]; then $doit $chowncmd $dsttmp; else true;fi &&
- if [ x"$chgrpcmd" != x ]; then $doit $chgrpcmd $dsttmp; else true;fi &&
- if [ x"$stripcmd" != x ]; then $doit $stripcmd $dsttmp; else true;fi &&
- if [ x"$chmodcmd" != x ]; then $doit $chmodcmd $dsttmp; else true;fi &&
-
-# Now rename the file to the real destination.
-
- $doit $rmcmd -f $dstdir/$dstfile &&
- $doit $mvcmd $dsttmp $dstdir/$dstfile
-
-fi &&
-
-
-exit 0
diff --git a/mksedscript b/mksedscript
@@ -1,236 +0,0 @@
-#! /bin/sh
-
-# Values from config.h
-
-mk_XAW=
-mk_MOTIF=
-mk_COLOR=
-mk_GREY=
-mk_BUTTONS=
-mk_MKTEXPK=
-mk_MAKETEXPK=
-mk_MKTEXPK_PATH=
-mk_PS_GS=
-mk_GS_PATH='gs'
-mk_PS_DPS=
-mk_PS_NEWS=
-mk_DEFAULT_CONFIG_PATH=
-mk_SELFAUTO=
-mk_EXTRA_APP_DEFAULTS=
-mk_DOSNAMES=
-mk_A4=
-mk_FREETYPE=
-mk_DEFAULT_TEXMF_PATH=
-mk_DEFAULT_FONT_PATH=
-mk_DEFAULT_VF_PATH=
-mk_DEFAULT_FIG_PATH=
-mk_DEFAULT_HEADER_PATH=
-mk_DEFAULT_DVIPS_CF_PATH=
-mk_DEFAULT_FONTMAP_PATH=
-mk_DEFAULT_ENC_PATH=
-mk_DEFAULT_TYPE1_PATH=
-mk_DEFAULT_GS_LIB_PATH=
-
-# Optional values from CFLAGS
-
-mk_MFMODE='unspecified'
-mk_BDPI=300
-mk_DEFAULT_FONT_SIZES='m0:m0.5:m1:m2:m3:m4:m5'
-mk_SHRINK=3
-mk_XDVIFONTS_ONLY=
-mk_MKPK_REDIRECT=
-
-# Get arguments from CFLAGS
-
-for mk_arg
-do
- case "$mk_arg" in
- -D*=*)
- eval "`echo \"$mk_arg\" | sed 's/^-D/mk_/'`"
- ;;
- -D*)
- eval "`echo \"$mk_arg\" | sed 's/^-D/mk_/'`=1"
- ;;
- esac
-done
-
-# Get arguments from config.h
-
-eval "`grep '^[ ]*#[ ]*define[ ]' config.h \
- | sed 's/^[ ]*#[ ]*define[ ][ ]*/mk_/' \
- | sed 's/[ ][ ]*/=/'`"
-
-# Process simple boolean arguments.
-
-if test -n "$mk_XAW" -o -n "$mk_MOTIF"; then echo 's/^#tool//';
- else mk_EXTRA_APP_DEFAULTS=; mk_BUTTONS=
- echo '/^#iftool/,/^#/d'; fi
-if test -z "$mk_COLOR"; then echo '/^#ifcolor/,/^#/d'; fi
-if test -z "$mk_GREY"; then echo '/^#ifgrey/,/^#/d'; fi
-if test -z "$mk_BUTTONS"; then echo '/^#ifbuttons/,/^#/d'; fi
-if test -z "$mk_PS_DPS"; then echo '/^#ifdps/,/^#/d'; fi
-if test -z "$mk_PS_NEWS"; then echo '/^#ifnews/,/^#/d'; fi
-if test -z "$mk_DOSNAMES"; then echo '/^#ifdosnames/,/^#/d'; fi
-if test -n "$mk_XDVIFONTS_ONLY";then echo '/^#iftexfonts/,/^#/d'; fi
-if test -z "$mk_FREETYPE"; then echo '/^#ifft/,/^#/d'; fi
-
-# Process arguments having to do with mktexpk/MakeTeXPK
-
-if test -n "$mk_MKTEXPK" || test -n "$mk_MAKETEXPK"; then
- if test -z "$mk_MKTEXPK_PATH"; then
- if test -n "$mk_MAKETEXPK"; then
- mk_MKTEXPK_PATH=MakeTeXPK
- else
- mk_MKTEXPK_PATH=mktexpk
- fi
- fi
- echo "s^@MKTEXPK_PATH@^$mk_MKTEXPK_PATH^"
- if test -n "$mk_MAKETEXPK"; then
- echo "s/@MKTEXPK_DEFAULT_MODE@/default/"
- if test -n "$mk_MKPK_REDIRECT"; then
- echo "s/@MKTEXPK_TAIL@/%n %d %b %m %o '' %r/"
- else
- echo "s/@MKTEXPK_TAIL@/%n %d %b %m %o/"
- fi
- else
- echo "s^@MKTEXPK_DEFAULT_MODE@^/^"
- echo "s/@MKTEXPK_TAIL@/--mfmode %o --bdpi %b --mag %m --dpi %d %n %r/"
- fi
-else
- echo '/^#ifmakepk/,/^#/d'
-fi
-
-# Process remaining PostScript emulation arguments
-
-if test -z "$mk_PS_GS"; then
- echo '/^#ifghost/,/^#/d'
-else
- echo "s^@GS_PATH@^$mk_GS_PATH^"
-fi
-
-if test -n "$mk_PS_GS" || test -n "$mk_PS_DPS" || test -n "$mk_PS_NEWS"; then
- mk_PS=y
- echo '/^#ifnops/,/^#/d'
-else
- mk_PS=
- echo '/^#ifps/,/^#/d'
-fi
-
-# Process arguments describing a config file
-
-if test -n "$mk_EXTRA_APP_DEFAULTS"; then
- mk_SELFAUTO=y
-else
- echo '/^#ifextraappdef/,/^#/d'
-fi
-
-if test -n "$mk_SELFAUTO"; then
- if test -z "$mk_DEFAULT_CONFIG_PATH"; then
- mk_DEFAULT_CONFIG_PATH='$SELFAUTODIR:$SELFAUTOPARENT'
- fi
-else
- echo '/^#ifselfauto/,/^#/d'
-fi
-
-# Miscellaneous args
-
-if test -n "$mk_A4"; then
- echo 's/@DEFAULT_PAGE_SIZE@/21 x 29.7 cm (A4 size)/'
- echo 's/@DEFAULT_UNIT@/cm " (centimeters)"/'
-else
- echo 's/@DEFAULT_PAGE_SIZE@/8.5 x 11 inches/'
- echo 's/@DEFAULT_UNIT@/in " (inches)"/'
-fi
-
-echo "s^@MFMODE@^$mk_MFMODE^"
-echo "s/@BDPI@/$mk_BDPI/"
-echo "s/@SHRINK@/$mk_SHRINK/"
-
-# Process paths.
-
-if test -z "$mk_DEFAULT_CONFIG_PATH"; then
- echo '/^#ifconfig/,/^#/d'
-else
- echo "s^@DEFAULT_CONFIG_PATH@ ^.TP 40\\
-.B $mk_DEFAULT_CONFIG_PATH\\
-^" | sed -e "s^:^\\\\\\
-.TP\\\\\\
-.B ^g"
-fi
-
-if test -z "$mk_DEFAULT_TEXMF_PATH"; then
- echo '/@DEFAULT_TEXMF_PATH@/d'
-else
- echo "s^@DEFAULT_TEXMF_PATH@ ^.TP 40\\
-.B $mk_DEFAULT_TEXMF_PATH\\
-^" | sed -e "s^:^\\\\\\
-.TP\\\\\\
-.B ^g"
-fi
-
-echo "s^@DEFAULT_FONT_PATH@ ^.B $mk_DEFAULT_FONT_PATH\\
-^" | sed -e "s@:@\\\\\\
-.TP\\\\\\
-.B @g"
-
-if test -z "$mk_DEFAULT_VF_PATH"; then
- echo '/@DEFAULT_VF_PATH@/d'
-else
- echo "s^@DEFAULT_VF_PATH@ ^.TP\\
-.B $mk_DEFAULT_VF_PATH\\
-^" | sed -e "s^:^\\\\\\
-.TP\\\\\\
-.B ^g"
-fi
-
-echo "s^@DEFAULT_FIG_PATH@ ^.B $mk_DEFAULT_FIG_PATH\\
-^" | sed -e "s^:^\\\\\\
-.TP\\\\\\
-.B ^g"
-
-echo "s^@DEFAULT_HEADER_PATH@ ^.B $mk_DEFAULT_HEADER_PATH\\
-^" | sed -e "s^:^\\\\\\
-.TP\\\\\\
-.B ^g"
-
-echo "s^@DEFAULT_DVIPS_CF_PATH@ ^.B $mk_DEFAULT_DVIPS_CF_PATH\\
-^" | sed -e "s^:^\\\\\\
-.TP\\\\\\
-.B ^g"
-
-echo "s^@DEFAULT_FONTMAP_PATH@ ^.B $mk_DEFAULT_FONTMAP_PATH\\
-^" | sed -e "s^:^\\\\\\
-.TP\\\\\\
-.B ^g"
-
-echo "s^@DEFAULT_ENC_PATH@ ^.B $mk_DEFAULT_ENC_PATH\\
-^" | sed -e "s^:^\\\\\\
-.TP\\\\\\
-.B ^g"
-
-echo "s^@DEFAULT_TYPE1_PATH@ ^.B $mk_DEFAULT_TYPE1_PATH\\
-^" | sed -e "s^:^\\\\\\
-.TP\\\\\\
-.B ^g"
-
-echo "s^@DEFAULT_GS_LIB_PATH@ ^.B $mk_DEFAULT_GS_LIB_PATH\\
-^" | sed -e "s^:^\\\\\\
-.TP\\\\\\
-.B ^g"
-
-echo "s/@DEFAULT_FONT_SIZES@/$mk_DEFAULT_FONT_SIZES/" | sed -e "s/:/ :\\\\\\
-/g"
-
-# Combination changes.
-
-if test -z "$mk_PS" || test -z "$mk_DEFAULT_CONFIG_PATH"; then
- echo '/^#ifconfigps/,/^#/d'
-fi
-
-# Remove all remaining '#' lines
-
-echo '/^#/d'
-
-# Done
-
-exit 0
