diff options
Diffstat (limited to 'Build')
| -rw-r--r-- | Build/source/texk/web2c/omegaware/ChangeLog | 4 | ||||
| -rw-r--r-- | Build/source/texk/web2c/omegaware/odvicopy.web | 26 |
2 files changed, 17 insertions, 13 deletions
diff --git a/Build/source/texk/web2c/omegaware/ChangeLog b/Build/source/texk/web2c/omegaware/ChangeLog index 3ea32a415ac..efa7c5b0ca5 100644 --- a/Build/source/texk/web2c/omegaware/ChangeLog +++ b/Build/source/texk/web2c/omegaware/ChangeLog @@ -1,3 +1,7 @@ +2018-07-22 Hironobu Yamashita <h.y.acetaminophen@gmail.com> + + * odvicopy.web: Sync with dvicopy.web change 2018-07-17 (typos). + 2018-01-19 Hironobu Yamashita <h.y.acetaminophen@gmail.com> * ovp2ovf.web, ovp2ovf.ch: Throw an error and exit if OFMLEVEL diff --git a/Build/source/texk/web2c/omegaware/odvicopy.web b/Build/source/texk/web2c/omegaware/odvicopy.web index 6f4e240c146..d31ff26b2ac 100644 --- a/Build/source/texk/web2c/omegaware/odvicopy.web +++ b/Build/source/texk/web2c/omegaware/odvicopy.web @@ -12,8 +12,7 @@ % any later version. % % You should have received a copy of the GNU General Public License -% along with this program; if not, write to the Free Software -% Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA. +% along with this program. If not, see <http://www.gnu.org/licenses/>. % % Version 0.9 was finished May 21, 1990. % Version 1.0 pixel rounding for real devices (August 6, 1990). @@ -27,6 +26,7 @@ % diagnose impossible cases (September 2009). % bug fix (not for Web2C) and some typos (May 2014) % from Udo Wermuth (u.wermuth@@icloud.com). +% 17 July 2018, still version 1.6: typos corrected, no code changes. % Here is TeX material that gets inserted after \input webmac \def\hang{\hangindent 3em\indent\ignorespaces} @@ -81,13 +81,13 @@ and (2)~it serves as an example of a program that reads \.{DVI}, \.{DVI}-related software. Goal number (1) is important since quite a few existing programs have -to be adapted to the extened capabilities of Version~3 of \TeX\ which +to be adapted to the extended capabilities of Version~3 of \TeX\ which will require some time. Moreover some existing programs are `as is' and the source code is, unfortunately, not available. Goal number (2) needs perhaps a bit more explanation. Programs for typesetting need to be especially careful about how they do arithmetic; if rounding errors accumulate, margins won't be straight, vertical rules -won't line up, and so on (see the documentaion of \.{DVItype} for more +won't line up, and so on (see the documentation of \.{DVItype} for more details). This program is written as if it were a \.{DVI}-driver for a hypothetical typesetting device |out_file|, the output file receiving the copy of the input |dvi_file|. In addition all code related to @@ -225,7 +225,7 @@ mostly by using several \.{WEB} coding tricks, such as not to make the resulting \PASCAL\ program inefficient in any way. Parts of the program that are needed in \.{DVIprint} but not in -\.{DVIcopy} are delimited by the codewords `$|device|\ldots|ecived|$'; +\.{DVIcopy} are delimited by the code words `$|device|\ldots|ecived|$'; these are mostly the pixel rounding algorithms used to convert the \.{DVI} units of a \.{DVI} file to the raster units of a real output device and have been copied more or less verbatim from \.{DVItype}. @@ -588,7 +588,7 @@ of systems that might want to use such information. the whole process must be aborted; \.{\title} will give up, after issuing an error message about what caused the error. These messages will, however, in most cases just indicate which input file caused the error. One of the -programs \.{DVItype}, \.{TFtoPL} or \.{VFtoVP} should then be used to +programs \.{DVItype}, \.{TFtoPL}, or \.{VFtoVP} should then be used to diagnose the error in full detail. Such errors might be discovered inside of subroutines inside of subroutines, @@ -2654,7 +2654,7 @@ id3(".")("V")("F")(vf_ext); {file name extension for \.{VF} files} id4(".")("O")("V")("F")(ovf_ext); {file name extension for \.{OVF} files} @ If a \.{VF} file is badly malformed, we say |bad_font|; this procedure -gives an error message which refers the user to \.{VFtoVP} and \.{OVPtoOVF}, +gives an error message which refers the user to \.{OVF2OVP} and \.{OVP2OVF}, and terminates \.{\title}. @<Cases for |bad_font|@>= @@ -3267,7 +3267,7 @@ Thus we introduce a slight extension of \.{DVItype}'s pixel rounding algorithm and hope that this extension will become part of the standard \.{DVItype} program in the near future: If a \.{DVI} file contains a |set_rule| command for a rule with the negative height |width_dimen|, -then this rule shall be treated in exactly the same way as a ficticious +then this rule shall be treated in exactly the same way as a fictitious character whose width is the width of that rule; as value of |width_dimen| we choose $-2^{31}$, the smallest signed 32-bit integer. @@ -3292,7 +3292,7 @@ difficult to introduce them; furthermore they are similar to those in It may be desirable to (optionally) specify all the options in the command line and skip the dialog with the user, provided the operating -system permits this. Here we just define the system-indepent part of the +system permits this. Here we just define the system-independent part of the code required for this possibility. Since a complete option (a keyword possibly followed by one or several parameters) may have embedded blanks it might be necessary to replace these blanks by some other separator, @@ -3488,7 +3488,7 @@ important, in this example. The number of pages is recorded in @!select_there:array[0..max_select-1,0..9] of boolean; @!select_vals:array[0..max_select-1] of 0..9; @!select_max:array[0..max_select-1] of int_32; -@!out_mag:int_32; {output maginfication} +@!out_mag:int_32; {output magnification} @!count:array[0..9] of int_32; {the count values on the current page} @!num_select:0..max_select; {number of page selection ranges specified} @!cur_select:0..max_select; {current page selection range} @@ -3542,12 +3542,12 @@ else if scan_keyword(str_select,3) then id3("m")("a")("g")(str_mag); id6("s")("e")("l")("e")("c")("t")(str_select); -@ A stack is used to keep track of the current horizonal and vertical +@ A stack is used to keep track of the current horizontal and vertical position, |h| and |v|, and the four registers |w|, |x|, |y|, and |z|; the register pairs |(w,x)| and |(y,z)| are maintained as arrays. @<Types...@>= -@!device @<Declare device dependend types@>@; @+ ecived @; @/ +@!device @<Declare device dependent types@>@; @+ ecived @; @/ @!stack_pointer=0..stack_size;@/ @!stack_index=1..stack_size;@/ @!pair_32=array[0..1] of int_32; {a pair of |int_32| variables} @@ -3611,7 +3611,7 @@ The horizontal escapement of character~|c| in font~|f| is given by @d max_pix_value==@"7FFF {largest allowed pixel value; this range may not suffice for high resolution output devices} -@<Declare device dependend types@>= +@<Declare device dependent types@>= @!pix_value=-max_pix_value..max_pix_value; {a pixel coordinate or displacement} @ @<Glob...@>= |