From 942e56ba7d147d18d379305e76f064cec0aade7d Mon Sep 17 00:00:00 2001
From: Norbert Preining
This file documents dvipng version 1.16 +
This file documents dvipng version 1.17
Corrections or perhaps rewrites of sections are very welcome.
@@ -124,7 +124,7 @@ Independent) file into PNG (Portable Network Graphics).This is ./dvipng 1.16 Copyright 2002-2015, 2019 Jan-Ake Larsson +This is ./dvipng 1.17 Copyright 2002-2015, 2019 Jan-Ake Larsson Usage: ./dvipng [OPTION]... FILENAME[.dvi] Options are chosen to be similar to dvips' options where possible: @@ -1285,7 +1285,7 @@ Georg Schwarz, Jason Farmer, Brian V. Smith, Samuel Hathaway, Thomas R. Shemanske, Stephen Gibson, Christian Ridderström, Ezra Peisach, William H Wheeler, Thomas Klausner, Harald Koenig, Adrian Bunk, Kevin Smith, Jason Riedy, Wolfram Krause, Reinhard Kotucha, Takeshi Abe, -Waldeck Schutzer, and Andy Nguyen. +Waldeck Schutzer, Ahzo, and Andy Nguyen.
diff --git a/systems/doc/dvipng/dvipng.pdf b/systems/doc/dvipng/dvipng.pdf index 08d644f0d3..e85e38e0ea 100644 Binary files a/systems/doc/dvipng/dvipng.pdf and b/systems/doc/dvipng/dvipng.pdf differ diff --git a/systems/doc/dvips/dvips.html b/systems/doc/dvips/dvips.html index c090e788a6..568dbae14b 100644 --- a/systems/doc/dvips/dvips.html +++ b/systems/doc/dvips/dvips.html @@ -1,9 +1,9 @@ - - +Dvips: A DVI-to-PostScript translator @@ -60,7 +60,7 @@ ul.no-bullet {list-style: none}
This manual documents Dvips version 5.999 -(February 2019), a program to translate a DVI file into +
This manual documents Dvips version 2020.1 +(January 2020), a program to translate a DVI file into PostScript. You may freely use, modify and/or distribute this file.
• Color | Using color with Dvips. | |
• Index | General index. + | |
• Index | General index. |
Turns bitmap font encoding to ‘off’, ‘on’ (no warnings +for missing bitmap font encodings), or ‘strict’ (with warnings +for missing bitmap font encodings). +
+Multiple copies. Same as ‘-b’, see Option details.
Turns bitmap font encoding to ‘off’, ‘on’ (no warnings +for missing bitmap font encodings), or ‘strict’ (with warnings +for missing bitmap font encodings). +
+Include filename as an additional configuration file, read @@ -3683,7 +3699,9 @@ i.e., renumbers, the characters of a font.
-Next: PostScript typesetting, Previous: Virtual fonts, Up: Font concepts [Contents][Index]
+Next: Bitmap font encodings, Previous: Virtual fonts, Up: Font concepts [Contents][Index]+Next: PostScript typesetting, Previous: Encodings, Up: Font concepts [Contents][Index]
+To dvips, bitmapped fonts do not have any notion of linguistics; they +are simply a vector of glyphs. By comparison, PostScript fonts are +required to contain an encoding vector that at least provides +glyph names; these names can permit PostScript and PDF viewers to +extract legible text from Postscript and PDF output. +
+Unlike previous versions, dvips versions 2020 and later add glyph
+naming information to Type 3 bitmapped fonts (if they can locate such
+information) as an Encoding vector. This provides some support for
+search, for copy and paste, and even some limited support for
+accessibility. The ‘bitmapfontenc’ command line option
+(see Option details and bitmapfontenc
configuration option
+(see Configuration file commands) enable and disable this
+functionality; by default it is set to enabled, without warnings.
+
To do this, dvips must find encoding information for the bitmapped +fonts. It does this by first searching for a font-specific encoding +file; for instance, for cmr10, it will search for dvips-cmr10.enc +in the standard encoding path. If it does not find such a file, it +will search for a dvips-all.enc file which contains a base set of +encodings for many fonts. +
+The specific syntax of an encoding file is unspecified, except that it +must be a PostScript fragment that leaves exactly one object on the +operand stack. (This is different from the encoding files used to +define encodings for PostScript fonts, described earlier). Normally +that object is just an array of 256 names; in this case, that array is +used as the encoding vector for the font. Alternatively, the object +can be a procedure that, when executed, leaves a legal encoding vector +on the stack. This second option is made available to support future +enhancements that may add additional constructs to the font dictionary +to enhance the interpretation of font characters. +
+The dvips-all.enc file contains encodings for many fonts, and +it is loaded by dvips at most once. The format is just a sequence of +font names, one per line, each terminated by a colon, followed by the +encoding to use for those files. +
+ + +As part of its operation, to enable heuristics in PostScript and +PDF viewers to properly identify word breaks and column gutters, +dvips also generates a modified font bounding box and a modified +font coordinate system. +
+-Previous: Encodings, Up: Font concepts [Contents][Index]
+Previous: Bitmap font encodings, Up: Font concepts [Contents][Index]-a
:-B
:-b num
:-bitmapfontenc option
:-c num
:-C num
:-c ratio
:bitmapfontenc config command (bitmap font encoding)
:bop-hook
:bop-hook
:dvihps, hyperdvi to PostScript
:dvips-all.enc
:dvips.enc
:DVIPSDEBUG
:DVIPSFONTS
:end-hook
:fontinst
:This manual documents the Kpathsea library for path searching. It -corresponds to version 6.3.1, released in -March 2019. +corresponds to version 6.3.2, released in +March 2020.
• Introduction | Overview and history. @@ -193,7 +193,7 @@ March 2019. | |
• Reporting bugs | Where and how to report bugs. | |
• Index | General index. + | |
• Index | General index. |
This manual corresponds to version 6.3.1 of the Kpathsea -library, released in March 2019. +
This manual corresponds to version 6.3.2 of the Kpathsea +library, released in March 2020.
The library’s fundamental purpose is to return a filename from a list of directories specified by the user, similar to what shells do when @@ -230,7 +230,7 @@ this library:
Other software that we do not maintain also uses it.
Kpathsea is now maintained as part of the TeX Live distribution -(http://tug.org/texlive), which includes several more +(https://tug.org/texlive), which includes several more Kpathsea-using programs. For information on configuration, building, installing, and more, see Building TeX Live.
@@ -251,7 +251,7 @@ along with any changes you have made, and allow anyone to modify the library source and distribute their modifications. It does not mean you have to distribute the source to your program using the library, although we hope you will. See accompanying files for the text of the -GNU licenses, or http2://www.gnu.org/licenses. +GNU licenses, or https://gnu.org/licenses.If you know enough about TeX to be reading this manual, then you (or
@@ -391,19 +391,20 @@ Next: Security, Previous:
This
-is https://tug.org/tex/unixtex.ftp, last updated 28 November
-2017. Email tex-k@tug.org with comments or questions.
+is ftp://tug.org/tex/unixtex.ftp, a.k.a.
+https://tug.org/unixtex.ftp, last updated 29 February 2020.
+Email tex-k@tug.org with comments or questions.
The principal free TeX distribution for Unix-like systems is TeX
Live, on the web at http://tug.org/texlive. The pages there
-describe many ways to acquire and.or build TeX, over the Internet
+describe many ways to acquire and/or build TeX, over the Internet
or on physical media, both the sources and precompiled binaries for
many systems, either standalone or as part of various operating system
distributions.
Web2c, Kpathsea, Dvips, and Dviljk are no longer released as a
-separate packages. Their sources are now maintained as part of TeX
-Live.
+ Web2c, Kpathsea, Dvips, and Dviljk, among others, are no longer
+released as a separate packages. Their sources are now maintained as
+part of TeX Live.
The host ftp.cs.stanford.edu is the original source for the files
for which Donald Knuth is directly responsible: tex.web,
plain.tex, etc. However, unless you want to undertake the
-project of building your TeX installation from scratch, it is more
+project of building your TeX system from scratch, it is more
reliable and less work to retrieve these files as part of a larger
package.
In short, here is a skeleton of the default directory structure, @@ -604,6 +605,12 @@ Next: TeX support, Previous: provides. For information about searching for particular file types (e.g., TeX fonts), see the next chapter.
+ +This section, with minor differences, has been translated into several +other languages (Chinese, Spanish, Russian, Japanese, French, German, +…) as part of the TeX Live guide; see +https://tug.org/texlive/doc.html for links. +
• Searching overview | Basic scheme for searching. | ||
- | |||
---|---|---|---|
--all : | Path searching options | ||
--casefold-search : | Path searching options | ||
--cnf-line : | Path searching options | ||
‘--cnf-line’, source for path : | Path sources | ||
--color=tty : | ls-R | ||
--debug=num : | Auxiliary tasks | ||
--dpi=num : | Path searching options | ||
.pool : | Supported file formats | ||
.pool : | Supported file formats | ||
.pro : | Supported file formats | ||
.progname qualifier in texmf.cnf : | Config files | ||
.rhosts, writable by TeX : | Security | ||
.ris : | Supported file formats | ||
.sfd : | Supported file formats | ||
: may not be : : | Searching overview | ||
:: expansion : | Default expansion | ||
| |||
\ | |||
; | |||
; translated to ‘:’ in texmf.cnf : | Config files | ||
| |||
= | |||
= omitted in texmf.cnf and misparsing : | Config files | ||
| |||
\ | |||
\, line continuation in texmf.cnf : | Config files | ||
\openin : | Searching overview | ||
\special, suppressing warnings about : | Suppressing warnings | ||
| |||
{ | |||
{ | |||
{ expansion : | Brace expansion | ||
| |||
~ | |||
~ | |||
~ expansion : | Tilde expansion | ||
| |||
A | |||
tolerance for glyph lookup: | Basic glyph lookup | ||
trailing ‘/’ in home directory: | Tilde expansion | ||
trailing colons: | Default expansion | ||
translations, of path searching description: | Path searching | ||
TRFONTS : | Supported file formats | ||
trick for detecting leaf directories: | Subdirectory expansion | ||
trojan horse attack: | Security |