diff options
Diffstat (limited to 'Build/source/texk/web2c')
-rw-r--r-- | Build/source/texk/web2c/ChangeLog | 10 | ||||
-rw-r--r-- | Build/source/texk/web2c/patgen.web | 8 | ||||
-rw-r--r-- | Build/source/texk/web2c/pktogf.web | 14 | ||||
-rw-r--r-- | Build/source/texk/web2c/pktype.web | 14 |
4 files changed, 31 insertions, 15 deletions
diff --git a/Build/source/texk/web2c/ChangeLog b/Build/source/texk/web2c/ChangeLog index b7d638f0ae7..f79873dc700 100644 --- a/Build/source/texk/web2c/ChangeLog +++ b/Build/source/texk/web2c/ChangeLog @@ -1,3 +1,13 @@ +2020-04-23 Tomas Rokicki <rokicki@gmail.com> + and Karl Berry <karl@freefriends.org> + + * patgen.web, + * pktogf.web, + * pktype.web: fix trivial typos and clarify public domain status. + No code changes. + (These .web files are not maintained by DEK, per + https://tug.org/TUGbpat/tb35-1/tb109knut.pdf page 2.) + 2020-04-13 Andreas Scherer <https://ascherer.github.io> * ctangleboot.cin: Add comment for section 6. diff --git a/Build/source/texk/web2c/patgen.web b/Build/source/texk/web2c/patgen.web index 5eae5b5a52d..a78d895c4f8 100644 --- a/Build/source/texk/web2c/patgen.web +++ b/Build/source/texk/web2c/patgen.web @@ -1,3 +1,4 @@ +% This program is not copyrighted and can be used freely. % This is PATGEN.WEB in text format, as of August 23, 2004. % Version 1.0 was finished in 1983. % Version 2.0 major revision for `8-bit TeX' (November 8, 1991). @@ -5,6 +6,7 @@ % Version 2.2 added `close_in(dictionary)' (August, 1996). % Version 2.3 avoided division by zero - Karl Berry (October, 1996). % Version 2.4 avoided use of uninitialized variables (September, 2009). +% A few typos fixed, no version change (April, 2020). % Here is TeX material that gets inserted after \input webmac \def\hang{\hangindent 3em\indent\ignorespaces} @@ -21,7 +23,7 @@ \vskip 8pt \centerline{\titlefont for the \TeX 82 hyphenator} \vskip 15pt - \centerline{(Version 2.4, September 2009)} + \centerline{(Version 2.4, April 2020)} \vfill} \pageno=\contentspagenumber \advance\pageno by 1 @@ -1070,7 +1072,7 @@ as \PASCAL\ string (i.e., as \&{packed} \&{array} |[1..any]| \&{of} @!buf_ptr: 0..max_buf_len; {index into |buf|} @ When an error is caused by bad input data we say |bad_input(#)| in -order to disply the contents of the |buf| array before terminating with +order to display the contents of the |buf| array before terminating with an error message. @d print_buf== {print contents of |buf| array} @@ -1177,7 +1179,7 @@ start with two equal characters (e.g., are blank) and are ignored. Other lines contain the external representation of the lower case version and an arbitrary number of `upper case versions' of a letter preceded and separated by a delimiter and followed by two consecutive -delimiters; the delimiter may be any character not occuring in either +delimiters; the delimiter may be any character not occurring in either version. @<Set up repres...@>= diff --git a/Build/source/texk/web2c/pktogf.web b/Build/source/texk/web2c/pktogf.web index 8fc8a0256f6..5b3ff04f8f1 100644 --- a/Build/source/texk/web2c/pktogf.web +++ b/Build/source/texk/web2c/pktogf.web @@ -1,3 +1,4 @@ +% This program is not copyrighted and can be used freely. % PKtoGF.web % % PKtoGF creates a generic font file from a packed pixel file. @@ -6,7 +7,8 @@ % Fixed bug to include specials in character (1.0): January 1988 % Cleaned up description (bitweight errors) no version change: July 1990 % Fixed bug with empty character setting min_n to 1 (1.1): 19 October 1990 -\def\versiondate{19 October 1990} +% A few typos, no version change: 22 April 2020 +\def\versiondate{22 April 2020} % \font\ninerm=cmr9 \let\mc=\ninerm % medium caps for names like PASCAL @@ -615,7 +617,7 @@ definitions are called flag bytes, and various fields within the byte indicate various things about how the character definition is encoded. Command bytes have zero or more parameters, and can never appear within a character definition or between parameters of another command, where they would be -interpeted as data. +interpreted as data. A \.{PK} file consists of a preamble, followed by a sequence of one or more character definitions, followed by a postamble. The preamble command must @@ -656,7 +658,7 @@ of a keyword followed by possible parameters relevant to that keyword. length exceeds~255. \yskip\hang\\{pk\_xxx4} 243 |k[4]| |x[k]|. Like |pk_xxx1|, but |k| can be -ridiculously large; |k| musn't be negative. +ridiculously large; |k| mustn't be negative. \yskip\hang|pk_yyy| 244 |y[4]|. This command is undefined in general; it functions as a five-byte \\{no\_op} unless special \.{PK} reading programs @@ -857,7 +859,7 @@ more bytes than this, although, of course, it is legal for any character. Any extra bits in the last byte should be set to zero. @ At this point, we are ready to introduce the format for a character -descripter. It consists of three parts: a flag byte, a character preamble, +descriptor. It consists of three parts: a flag byte, a character preamble, and the raster data. The most significant four bits of the flag byte yield the |dyn_f| value for that character. (Notice that only values of 0 through 14 are legal for |dyn_f|, with 14 indicating a bit mapped character; @@ -902,7 +904,7 @@ parameters of the \.{GF} file format, including vertical escapement. \vskip\baselineskip The |flag| parameter is the flag byte. The parameter |pl| (packet length) contains the offset -of the byte following this character descripter, with respect to the beginning +of the byte following this character descriptor, with respect to the beginning of the |tfm| width parameter. This is given so a \.{PK} reading program can, once it has read the flag byte, packet length, and character code (|cc|), skip over the character by simply reading this many more bytes. For the two short @@ -1042,7 +1044,7 @@ text files and files of bytes (packed files and generic font files.) For our purposes, we shall consider an eight-bit byte to consist of the values |0..255|. If your system does not pack these values to a byte, it is no major difficulty; you must only insure that the input function -|pk_byte| can read packed bytes, and that the output fuunction |gf_byte| +|pk_byte| can read packed bytes, and that the output function |gf_byte| packs the bytes to be shipped. @<Types...@>= diff --git a/Build/source/texk/web2c/pktype.web b/Build/source/texk/web2c/pktype.web index eac85ee36f6..6323dc453a9 100644 --- a/Build/source/texk/web2c/pktype.web +++ b/Build/source/texk/web2c/pktype.web @@ -1,3 +1,4 @@ +% This program is not copyrighted and can be used freely. % PKtype.web % % PKtype verifies the correctness of a PK file. @@ -8,11 +9,12 @@ % Updated again for new pk format, 2.1 version: 15 August 1985 % Docmentation updated, 2.2 version: 17 November 1987 % -% slight editing to correspond with MFware report -- don, 21 Oct 89 -% additional editing suggested by P Breitenlohner -- don, 18 Nov 89 -% Corrected two typos -- 21 Dec 96 (don) +% slight editing to correspond with MFware report -- don, 21 October 89 +% additional editing suggested by P Breitenlohner -- don, 18 November 89 +% Corrected two typos -- 21 December 96 (don) +% More typos -- 23 April 20 (tgr/karl) -\def\versiondate{18 November 1989} +\def\versiondate{23 April 2020} % \def\hang{\hangindent 3em\noindent\ignorespaces} \font\ninerm=cmr9 @@ -301,7 +303,7 @@ definitions are called flag bytes, and various fields within the byte indicate various things about how the character definition is encoded. Command bytes have zero or more parameters, and can never appear within a character definition or between parameters of another command, where they would be -interpeted as data. +interpreted as data. A \.{PK} file consists of a preamble, followed by a sequence of one or more character definitions, followed by a postamble. The preamble command must @@ -342,7 +344,7 @@ of a keyword followed by possible parameters relevant to that keyword. length exceeds~255. \yskip\hang\\{pk\_xxx4} 243 |k[4]| |x[k]|. Like |pk_xxx1|, but |k| can be -ridiculously large; |k| musn't be negative. +ridiculously large; |k| mustn't be negative. \yskip\hang|pk_yyy| 244 |y[4]|. This command is undefined in general; it functions as a five-byte \\{no\_op} unless special \.{PK} reading programs |