summaryrefslogtreecommitdiff
path: root/Build/source/texk/dvipsk
diff options
context:
space:
mode:
authorKarl Berry <karl@freefriends.org>2009-12-24 18:38:47 +0000
committerKarl Berry <karl@freefriends.org>2009-12-24 18:38:47 +0000
commit6a8a6fa9af6af314e192d593ec496d112f909ff8 (patch)
tree46f8336570cd5461192ad4e37e02c97160440a70 /Build/source/texk/dvipsk
parent3b60c7b05b84cf460b6dd9f9f1b34e3363b59f6f (diff)
replace @mail.tug.org with just @tug.org
git-svn-id: svn://tug.org/texlive/trunk@16497 c570f23f-e606-0410-a88d-b1316a301751
Diffstat (limited to 'Build/source/texk/dvipsk')
-rw-r--r--Build/source/texk/dvipsk/AUTHORS5
-rw-r--r--Build/source/texk/dvipsk/ChangeLog5
-rw-r--r--Build/source/texk/dvipsk/INSTALL358
-rw-r--r--Build/source/texk/dvipsk/README32
-rw-r--r--Build/source/texk/dvipsk/contrib/config.proto2
-rw-r--r--Build/source/texk/dvipsk/dvips.16
-rw-r--r--Build/source/texk/dvipsk/dvips.info148
7 files changed, 95 insertions, 461 deletions
diff --git a/Build/source/texk/dvipsk/AUTHORS b/Build/source/texk/dvipsk/AUTHORS
index b934b590617..104d44e89e9 100644
--- a/Build/source/texk/dvipsk/AUTHORS
+++ b/Build/source/texk/dvipsk/AUTHORS
@@ -1,5 +1,6 @@
-This program, dvipsk, was modified by kb@mail.tug.org from Tom Rokicki's
-dvips distribution. Send bug reports to tex-k@mail.tug.org, not to Tom.
+This program, dvipsk, was originally modified by Karl Berry from Tom
+Rokicki's dvips distribution. Send bug reports to tex-k@tug.org,
+not to Tom personally.
Jim Hafner originally implemented the color support.
Sergey Lesenko originally implemented the partial Type 1 font downloading.
diff --git a/Build/source/texk/dvipsk/ChangeLog b/Build/source/texk/dvipsk/ChangeLog
index 5bdc30a6971..5c90b028eda 100644
--- a/Build/source/texk/dvipsk/ChangeLog
+++ b/Build/source/texk/dvipsk/ChangeLog
@@ -1,3 +1,8 @@
+2009-12-24 Karl Berry <karl@tug.org>
+
+ * AUTHORS, README, dvips.1, contrib/config.proto: doc updates.
+ * INSTALL: remove, completely stale.
+
2009-12-22 Karl Berry <karl@tug.org>
* debug.h (D_MEM): disable completely by defining to 0.
diff --git a/Build/source/texk/dvipsk/INSTALL b/Build/source/texk/dvipsk/INSTALL
deleted file mode 100644
index 27779ae5371..00000000000
--- a/Build/source/texk/dvipsk/INSTALL
+++ /dev/null
@@ -1,358 +0,0 @@
-Contents:
-
-Installation
- `config.ps' installation
- PostScript font installation
- Ghostscript installation
- Diagnosing problems
- Debug options
- No output at all
- Output too small or inverted
- Error messages from printer
- Long documents fail to print
- Including graphics fails
-
-
-Installation
-************
-
- (A copy of this chapter is in the distribution file `dvipsk/INSTALL'.)
-
- Installing Dvips is mostly the same as installing any Kpathsea-using
-program. Therefore, for the basic steps involved, *note Installation:
-(kpathsea)Installation.. (A copy is in the file `kpathsea/INSTALL'.)
-
- For solutions to common installation problems and information on how
-to report a bug, see the file `kpathsea/BUGS' (*note Bugs:
-(kpathsea)Bugs.). For solutions to Dvips-specific problems, *note
-Debug options::.. Also see the Dvips home page at
-`http://www.radicaleye.com/dvips'.
-
- Dvips does require some additional installation, detailed in the
-sections below. Also, to configure color devices, *note Color device
-configuration::..
-
-`config.ps' installation
-========================
-
- Dvips has its own configuration files: a file `config.ps' for
-sitewide defaults, and a file `config.PRINTER' for each printer (output
-device). Since these are site-specific, `make install' does not create
-them; you must create them yourself.
-
- (These Dvips configuration files are independent of the Kpathsea
-onfiguration file `texmf.cnf' (*note Config files: (kpathsea)Config
-files.).
-
- Dvips configuration files contents and searching are described fully
-in *Note Config files::. The simplest way to create a new
-configuration file is to copy and modify the file
-`dvipsk/contrib/config.proto', seasoning with options to your taste
-from *Note Config files::. Here is `config.proto' for your reading
-pleasure:
- % Prototype Dvips configuration file.
-
- % How to print, maybe with lp instead lpr, etc.
- o |lpr
-
- % Default resolution of this device, in dots per inch.
- D 600
-
- % Metafont mode. (This is completely different from the -M command-line
- % option, which controls whether mktexpk is invoked.) Get
- % `ftp://ftp.tug.org/tex/modes.mf' for a list of mode names. This mode
- % and the D number above must agree, or mktexpk will get confused.
- M ljfour
-
- % Memory available. Download the three-line PostScript file:
- % %! Hey, we're PostScript
- % /Times-Roman findfont 30 scalefont setfont 144 432 moveto
- % vmstatus exch sub 40 string cvs show pop showpage
- % to determine this number. (It will be the only thing printed.)
- m 3500000
-
- % Correct printer offset. You can use testpage.tex from the LaTeX
- % distribution to find these numbers. Print testpage.dvi more than once.
- O 0pt,0pt
-
- % Partially download Type 1 fonts by default. Only reason not to do
- % this is if you encounter bugs. (Please report them to
- % <tex-k@mail.tug.org> if you do.)
- j
-
- % Also look for fonts at these resolutions.
- R 300 600
-
- % With a high resolution and a RISC cpu, better to compress the bitmaps.
- Z
-
- % Uncomment these if you have and want to use PostScript versions of the
- % fonts.
- %p +cmfonts.map
- %p +lafonts.map
- %p +cyrfonts.map
- %p +eufonts.map
-
- % You will also want definitions for alternative paper sizes -- A4,
- % legal, and such. Examples in `contrib/papersize.level2' and
- % `contrib/papersize.simple'.
-
-PostScript font installation
-============================
-
- To use PostScript fonts with TeX and Dvips, you need both metric
-files (`.tfm' and `.vf') and the outlines (`.pfa' or `.pfb'). *Note
-Font concepts::.
-
- To support the basic PostScript font set, the recommended (and
-simplest) approach is to retrieve
-`ftp://ftp.tug.org/tex/psfonts.tar.gz' and unpack it in your
-`$(fontdir)' directory (`/usr/local/share/texmf/fonts' by default).
-This archive contains metrics, outlines, and bitmaps (for previewing)
-for the 35 de facto standard fonts donated by URW and the additional
-high-quality freely available PostScript fonts donated by Adobe,
-Bitstream, and URW, including geometrically-created variants such as
-oblique and small caps.
-
- `CTAN:/fonts/psfonts' contains support for many additional fonts for
-which you must buy outlines (Adobe, Bigelow & Holmes, Monotype,
-Softkey, Y&Y). `psfonts.tar.gz' is a small extract from this
-directory. (For CTAN info, *note unixtex.ftp: (kpathsea)unixtex.ftp.;
-a copy is in the top-level file `INSTALL'.)
-
- If you have additional PostScript fonts, you can make them available
-to Dvips by (1) giving them with appropriate filenames; and (2) running
-Afm2tfm (*note Making a font available::.) to make TFM and VF metrics
-for TeX and Dvips to use. Also add them to `psfonts.map' if necessary
-(*note psfonts.map::.); it contains everything contained in
-`psfonts.tar.gz' and most fonts that come with Unix systems.
-
- Following are locations for vendor-supplied fonts. Please mail
-<tex-k@mail.tug.org> if you find fonts elsewhere on your system.
-
-DEC Ultrix
- /usr/lib/DPS/outline/decwin
-
-DEC Digital Unix
- /usr/lib/X11/fonts/Type1Adobe
-
-HP HP-UX 9, 10
- /usr/lib/X11/fonts/type1.st/typefaces
-
-IBM AIX
- /usr/lpp/DPS/fonts/outlines
- /usr/lpp/X11/lib/X11/fonts/Type1
- /usr/lpp/X11/lib/X11/fonts/Type1/DPS
-
-NeXT
- /NextLibrary/Fonts/outline
-
-SGI IRIX
- /usr/lib/DPS/outline/base /usr/lib/X11/fonts/Type1
-
-Sun SunOS 4.x
- (NeWSprint only)
- newsprint_2.5/SUNWsteNP/reloc/$BASEDIR/
- NeWSprint/small_openwin/lib/fonts
- /usr/openwin/lib/X11/fonts/Type1/outline
-
-Sun Solaris 2
- /usr/openwin/lib/X11/fonts/Type1/outline
-
-VMS
- SYS$COMMON:[SYSFONT.XDPS.OUTLINE]
-
-The NeXT system supplies more fonts than any others, but there's a lot
-of overlap.
-
- Finally, if you have an Hewlett-Packard printer, you should be able to
-get Type 1 font files for the standard 35 fonts from HP, if the freely
-available URW Type 1's do not satisfy for whatever reason. The phone
-number for HP Printer Drivers is (in the United States) 303-339-7009.
-The driver set to ask for is Adobe Type Manager 2.51, and the disk set
-number is `MP210en3'. Mentioning anything other than Microsoft Windows
-when you ask for the driver set will likely lead to great confusion on
-the other end.
-
-Ghostscript installation
-========================
-
- Ghostscript is a PostScript interpreter freely available to end-users,
-written by Peter Deutsch. It can read the PostScript produced by Dvips
-and render it on your monitor, or for another device (e.g., an Epson
-printer) that does not support PostScript, or in PDF format. The latest
-version is available via `http://www.cs.wisc.edu/~ghost/index.html' and
-`ftp://ftp.cs.wisc.edu/pub/ghost/aladdin/'.
-
- A somewhat older version of Ghostscript is available under the GNU
-General Public License, free to everyone. You can get that from
-`ftp://prep.ai.mit.edu/pub/gnu/'.
-
- The program Ghostview, written by Tim Theisen, provides typical
-previewing capabilities (next page/previous page, magnification, etc.).
-It requires Ghostscript to run, and files in structured Postscript,
-specifically with `%%Page' comments (no `N' in `config.ps'). You can
-get Ghostview from the same places as Ghostscript.
-
-Diagnosing problems
-===================
-
- You've gone through all the trouble of installing Dvips, carefully
-read all the instructions in this manual, and still can't get something
-to work. The following sections provide some helpful hints if you find
-yourself in such a situation.
-
- For details on effective bug reporting, common installation problems,
-and `mktexpk' problems, *note Bugs: (kpathsea)Bugs..
-
-Debug options
--------------
-
- The `-d' flag to Dvips helps in tracking down certain errors. The
-parameter to this flag is an integer that tells what errors are
-currently being tracked. To track a certain class of debug messages,
-simply provide the appropriate number given below; if you wish to track
-multiple classes, sum the numbers of the classes you wish to track. To
-track all classes, you can use `-1'. Another useful value is `3650',
-which tracks everything having to do with file searching and opening.
-
- Some of these debugging options are actually provided by Kpathsea
-(*note Debugging: (kpathsea)Debugging.).
-
- The classes are:
-1
- specials
-
-2
- paths
-
-4
- fonts
-
-8
- pages
-
-16
- headers
-
-32
- font compression
-
-64
- files
-
-128
- config files
-
-256
- Partial Type 1 font encoding vectors
-
-512
- Partial Type 1 subr calls
-
-1024
- Kpathsea `stat' calls
-
-2048
- Kpathsea hash table lookups
-
-4096
- Kpathsea path element expansion
-
-8192
- Kpathsea path searches
-
-No output at all
-----------------
-
- If you are not getting any output at all, even from the simplest
-one-character file (for instance, `\ \bye'), then something is very
-wrong. Practically any file sent to a PostScript laser printer should
-generate some output, at the very least a page detailing what error
-occurred, if any. Talk to your system administrator about downloading a
-PostScript error handler. (Adobe distributes a good one called
-`ehandler.ps'.)
-
- It is possible, especially if you are using non-Adobe PostScript, that
-your PostScript interpreter is broken. Even then it should generate an
-error message. Dvips tries to work around as many bugs as possible in
-common non-Adobe PostScript interpreters, but doubtless it misses a few.
-PowerPage Revision 1, Interpreter Version 20001.001, on a Mitsubishi
-Shinko CHC-S446i color thermal dye sublimation printer is known to be
-unable to print with any but builtin fonts.
-
- If Dvips gives any strange error messages, or compilation on your
-machine generated a lot of warnings, perhaps the Dvips program itself is
-broken. Try using the debug options to determine where the error
-occurred (*note Debug options::.).
-
- It is possible your spooler is broken and is misinterpreting the
-structured comments. Try the `-N' flag to turn off structured comments
-and see what happens.
-
-Output too small or inverted
-----------------------------
-
- If some documents come out inverted or too small, probably your
-spooler is not supplying an end of job indicator at the end of each
-file. (This commonly happens on small machines that don't have
-spoolers.) You can force Dvips to do this with the `-F' flag (or `F'
-config file option), but this generates files with a terminating binary
-character (control-D). You can also try using the `-s' flag (or `s'
-config file option) to enclose the entire job in a save/restore pair.
-*Note Command-line options::, and *Note Config files::.
-
-Error messages from printer
----------------------------
-
- If your printer returns error messages, the error message gives very
-good information on what might be going wrong. One of the most common
-error messages is `bop undefined'. This is caused by old versions of
-Transcript and other spoolers that do not properly parse the setup
-section of the PostScript. To fix this, turn off structured comments
-with the `-N' option, but it'd be best to get your spooling software
-updated.
-
- Another error message is `VM exhausted'. Some printers indicate this
-error by locking up, others quietly reset. This is caused by Dvips
-thinking that the printer has more memory than it actually does, and
-then printing a complicated document. To fix this, try lowering the
-`m' parameter in the configuration file; use the debug option to make
-sure you adjust the correct file.
-
- Other errors may indicate you are trying to include graphics that
-don't nest properly in other PostScript documents, among other things.
-Try the PostScript file on a QMS PS-810 or other Adobe PostScript
-printer if you have one, or Ghostscript (*note Ghostscript
-installation::.); it might be a problem with the printer itself.
-
-Long documents fail to print
-----------------------------
-
- This is usually caused by incorrectly specifying the amount of memory
-the printer has in the configuration file; see the previous section.
-
-Including graphics fails
-------------------------
-
- The most common problem with including graphics is an incorrect
-bounding box (*note Bounding box::.). Complain to whoever wrote the
-software that generated the file if the bounding box is indeed
-incorrect.
-
- Another possible problem is that the figure you are trying to include
-does not nest properly; there are certain rules PostScript applications
-must follow when generating files to be included. The Dvips program
-includes work-arounds for such errors in Adobe Illustrator and other
-programs, but there are certainly applications that haven't been tested.
-
- One possible thing to try is the `-K' flag which strips the comments
-from an included figure. This might be necessary if the PostScript
-spooling software does not read the structured comments correctly. Use
-of this flag will break graphics from some applications, though, since
-some applications read the PostScript file from the input stream,
-looking for a particular comment.
-
- Any application which generates graphics output containing raw binary
-(not ASCII hex) will probably fail with Dvips.
-
diff --git a/Build/source/texk/dvipsk/README b/Build/source/texk/dvipsk/README
index 48c4cc4eb26..9e3d6860519 100644
--- a/Build/source/texk/dvipsk/README
+++ b/Build/source/texk/dvipsk/README
@@ -1,31 +1,17 @@
-This directory contains Dvipsk, my (kb@mail.tug.org) modified version of
-Tom Rokicki's dvips, a DVI-to-PostScript translator.
+This directory contains Dvipsk, a modified version of
+Tom Rokicki's dvips, a DVI-to-PostScript translator. This has become
+the only maintained Dvips, and functions as the original.
-See `NEWS' for major changes by release, `ChangeLog` for all changes.
-See `INSTALL' for installation instructions.
+See `ChangeLog` for all changes.
See `../kpathsea/BUGS' for details on reporting bugs.
-AT LEAST NEWS, ChangeLog, AND INSTALL ARE WOEFULLY OUT OF DATE.
-Aside from configuration, this differs from the original primarily in
-that it uses the same code for path searching as TeX and my other
-distributions.
-
-Dvipsk does not install any default config.ps file, since no one file is
-generally suitable. Sample Dvips config files are in the contrib/
-directory. See ./INSTALL.
-
-The documentation is now in Texinfo format. I've removed the font
-naming section, since it was an old version of the font naming document
-(which you can get from ftp://ftp.tug.org/tex/fontname/).
+Dvipsk does not install by itself any default config.ps file, since no
+one file is generally suitable. Sample Dvips config files are in the
+contrib/ directory.
Dvipsk is free software; Tom's original files are public domain. The
-files I wrote (originally for the Free Software Foundation) are covered
-by the GNU General Public License -- see the files COPYING*.
-
-You can get the original dvips from ftp://labrea.stanford.edu/pub/dvips*.
-
-kb@mail.tug.org
-Member of the League for Programming Freedom -- write lpf@uunet.uu.net.
+files Karl wrote (originally for the Free Software Foundation) are
+covered by the GNU General Public License -- see the files COPYING*.
-------------------------------------------------------------------------
dvips 5.86 notes:
diff --git a/Build/source/texk/dvipsk/contrib/config.proto b/Build/source/texk/dvipsk/contrib/config.proto
index 3033dce6afe..51a633acb5d 100644
--- a/Build/source/texk/dvipsk/contrib/config.proto
+++ b/Build/source/texk/dvipsk/contrib/config.proto
@@ -25,7 +25,7 @@ O 0pt,0pt
% Partially download Type 1 fonts by default. Only reason not to do
% this is if you encounter bugs. (Please report them to
-% @email{tex-k@@mail.tug.org} if you do.)
+% @email{tex-k@@tug.org} if you do.)
j
% Also look for fonts at these resolutions.
diff --git a/Build/source/texk/dvipsk/dvips.1 b/Build/source/texk/dvipsk/dvips.1
index 09170168cd8..0eb42aa8ce5 100644
--- a/Build/source/texk/dvipsk/dvips.1
+++ b/Build/source/texk/dvipsk/dvips.1
@@ -1,4 +1,4 @@
-.TH DVIPS 1 "27 May 2004"
+.TH DVIPS 1 "24 December 2009"
.SH NAME
dvips \- convert a TeX DVI file to PostScript
.SH SYNOPSIS
@@ -13,7 +13,7 @@ See the Texinfo documentation instead.
You can read it either in Emacs or with the standalone
.B info
program which comes with the GNU texinfo distribution as
-prep.ai.mit.edu:pub/gnu/texinfo*.tar.gz.
+ftp.gnu.org:pub/gnu/texinfo*.tar.gz.
.PP
The program
.B dvips
@@ -520,4 +520,4 @@ PostScript is a registered trademark of Adobe Systems Incorporated.
.SH AUTHOR
Tomas Rokicki <rokicki@cs.stanford.edu>; extended to virtual fonts
by Don Knuth. Path searching and configuration modifications by
-kb@mail.tug.org.
+Karl Berry.
diff --git a/Build/source/texk/dvipsk/dvips.info b/Build/source/texk/dvipsk/dvips.info
index 007024dca84..db7f1626fe5 100644
--- a/Build/source/texk/dvipsk/dvips.info
+++ b/Build/source/texk/dvipsk/dvips.info
@@ -180,7 +180,7 @@ pleasure:
% Partially download Type 1 fonts by default. Only reason not to do
% this is if you encounter bugs. (Please report them to
- % <tex-k@mail.tug.org> if you do.)
+ % <tex-k@tug.org> if you do.)
j
% Also look for fonts at these resolutions.
@@ -4707,78 +4707,78 @@ Node: Top564
Node: Why Dvips1313
Node: Installation4761
Node: config.ps installation5899
-Node: PostScript font installation8441
-Node: Ghostscript installation11315
-Node: Diagnosing problems12412
-Node: Debug options13507
-Node: No output14710
-Node: Small or inverted16178
-Node: Printer errors16897
-Node: Long documents fail18229
-Node: Including graphics fails18570
-Node: Invoking Dvips19808
-Node: Basic usage20399
-Node: Command-line options21383
-Node: Option summary21832
-Node: Option details23994
-Node: Environment variables42998
-Node: Config files45957
-Node: Configuration file searching46640
-Node: Configuration file commands49940
-Node: Paper size and landscape57053
-Node: papersize special58651
-Node: Config file paper sizes60060
-Node: Paper trays64215
-Node: Interaction with PostScript65549
-Node: PostScript figures66202
-Node: Bounding box66928
-Node: \includegraphics70299
-Node: EPSF macros72590
-Node: EPSF scaling74560
-Node: EPSF clipping77130
-Node: psfile special77772
-Node: Dynamic creation of graphics80165
-Node: Fonts in figures81483
-Node: Header files83143
-Node: Including headers from TeX84349
-Node: Including headers from the command line86383
-Node: Headers and memory usage87483
-Node: Literal PS88193
-Node: " special88775
-Node: ps special89516
-Node: Literal headers91014
-Node: PostScript hooks91729
-Node: Literal examples93819
-Node: Hypertext95271
-Node: Hypertext caveats96829
-Node: Hypertext specials101226
-Node: PostScript fonts103860
-Node: Font concepts104976
-Node: Metric files106143
-Node: Glyph files108969
-Node: Virtual fonts111325
-Node: Encodings113215
-Node: PostScript typesetting115597
-Node: Making a font available118679
-Node: Invoking afm2tfm123709
-Node: Changing font encodings124679
-Node: Changing TeX encodings125469
-Node: Changing PostScript encodings126569
-Node: Changing both encodings127913
-Node: Reencoding with Afm2tfm128586
-Node: Encoding file format131690
-Node: Special font effects135893
-Node: Afm2tfm options138156
-Node: psfonts.map141141
-Node: Color145873
-Node: Color macro files146917
-Node: User-definable colors150115
-Node: Color subtleties151390
-Node: Ted Turner153041
-Node: Color device configuration154266
-Node: Color support details156708
-Node: Color specifications157086
-Node: Color specials158489
-Node: Index160618
+Node: PostScript font installation8436
+Node: Ghostscript installation11310
+Node: Diagnosing problems12407
+Node: Debug options13502
+Node: No output14705
+Node: Small or inverted16173
+Node: Printer errors16892
+Node: Long documents fail18224
+Node: Including graphics fails18565
+Node: Invoking Dvips19803
+Node: Basic usage20394
+Node: Command-line options21378
+Node: Option summary21827
+Node: Option details23989
+Node: Environment variables42993
+Node: Config files45952
+Node: Configuration file searching46635
+Node: Configuration file commands49935
+Node: Paper size and landscape57048
+Node: papersize special58646
+Node: Config file paper sizes60055
+Node: Paper trays64210
+Node: Interaction with PostScript65544
+Node: PostScript figures66197
+Node: Bounding box66923
+Node: \includegraphics70294
+Node: EPSF macros72585
+Node: EPSF scaling74555
+Node: EPSF clipping77125
+Node: psfile special77767
+Node: Dynamic creation of graphics80160
+Node: Fonts in figures81478
+Node: Header files83138
+Node: Including headers from TeX84344
+Node: Including headers from the command line86378
+Node: Headers and memory usage87478
+Node: Literal PS88188
+Node: " special88770
+Node: ps special89511
+Node: Literal headers91009
+Node: PostScript hooks91724
+Node: Literal examples93814
+Node: Hypertext95266
+Node: Hypertext caveats96824
+Node: Hypertext specials101221
+Node: PostScript fonts103855
+Node: Font concepts104971
+Node: Metric files106138
+Node: Glyph files108964
+Node: Virtual fonts111320
+Node: Encodings113210
+Node: PostScript typesetting115592
+Node: Making a font available118674
+Node: Invoking afm2tfm123704
+Node: Changing font encodings124674
+Node: Changing TeX encodings125464
+Node: Changing PostScript encodings126564
+Node: Changing both encodings127908
+Node: Reencoding with Afm2tfm128581
+Node: Encoding file format131685
+Node: Special font effects135888
+Node: Afm2tfm options138151
+Node: psfonts.map141136
+Node: Color145868
+Node: Color macro files146912
+Node: User-definable colors150110
+Node: Color subtleties151385
+Node: Ted Turner153036
+Node: Color device configuration154261
+Node: Color support details156703
+Node: Color specifications157081
+Node: Color specials158484
+Node: Index160613

End Tag Table