From 887bfffd417c5b4c794b80801fbce4538c049e0c Mon Sep 17 00:00:00 2001 From: Karl Berry Date: Fri, 27 Nov 2020 21:38:14 +0000 Subject: mf2pt1 (27nov20) git-svn-id: svn://tug.org/texlive/trunk@57018 c570f23f-e606-0410-a88d-b1316a301751 --- Master/texmf-dist/doc/info/mf2pt1.info | 127 +++++++++++++++++---------------- 1 file changed, 67 insertions(+), 60 deletions(-) (limited to 'Master/texmf-dist/doc/info') diff --git a/Master/texmf-dist/doc/info/mf2pt1.info b/Master/texmf-dist/doc/info/mf2pt1.info index 4e091d1c793..88b8792718c 100644 --- a/Master/texmf-dist/doc/info/mf2pt1.info +++ b/Master/texmf-dist/doc/info/mf2pt1.info @@ -1,6 +1,6 @@ -This is mf2pt1.info, produced by makeinfo version 5.2 from mf2pt1.texi. +This is mf2pt1.info, produced by makeinfo version 6.7 from mf2pt1.texi. -Copyright (C) 2014 Scott Pakin +Copyright (C) 2005-2020 Scott Pakin @@ -11,7 +11,7 @@ or (at your option) any later version. The latest version of this license is in: - + and version 1.3c or later is part of all distributions of LaTeX version 2006/05/20 or later. @@ -47,13 +47,13 @@ File: mf2pt1.info, Node: Introduction, Next: Usage, Prev: Top, Up: Top Metafont is a high-level, mathematically oriented language for producing fonts. The Metafont interpreter produces device-dependent bitmaps, which render well at the target resolution on the target device, but -poorly at other resolutions or on other devices. Adobe's PostScript Type 1 -font format is the de facto font standard for printers these days. It -is a vector format, which implies that it scales better than bitmaps, -and it delegates the device- and resolution-dependent tweaking from the -font source to the target device's PostScript renderer. However, Type 1 -fonts are extremely difficult to code by hand. Usually, one uses a -WYSIWYG program to design a Type 1 font. Metafont, with its +poorly at other resolutions or on other devices. Adobe's PostScript +Type 1 font format is the de facto font standard for printers these +days. It is a vector format, which implies that it scales better than +bitmaps, and it delegates the device- and resolution-dependent tweaking +from the font source to the target device's PostScript renderer. +However, Type 1 fonts are extremely difficult to code by hand. Usually, +one uses a WYSIWYG program to design a Type 1 font. Metafont, with its font-specific programming language, is an elegant alternative. A font designer can write reusable subroutines for repeated features, such as serifs and accents. He can define a font in terms of arbitrary @@ -105,12 +105,11 @@ FontForge (optional) especially at lower resolutions. Perl is available from the Comprehensive Perl Archive Network -(http://www.cpan.org); MetaPost and the Type 1 utilities are available -from the Comprehensive TeX Archive Network (http://www.ctan.org); and, -FontForge is available from . In -addition, MetaPost's home page is -, and the Type 1 -utilities' home page is . +(https://www.cpan.org); MetaPost and the Type 1 utilities are available +from the Comprehensive TeX Archive Network (https://www.ctan.org); and +FontForge is available from . In +addition, MetaPost's home page is , and +the Type 1 utilities' home page is . Besides being useful for autohinting fonts, FontForge enables a font designer to hint fonts manually for additional fine-tuning and to @@ -164,8 +163,8 @@ N.B. The 'install-info' command is a convenient way to install page is embedded within the 'mf2pt1' Perl script and can be extracted with 'pod2man': - pod2man --center="User Commands" --date="30 April 2014" \ - --release="v2.5a" mf2pt1 > mf2pt1.1 + pod2man --center="User Commands" --date="27 November 2020" \ + --release="v2.6" mf2pt1 > mf2pt1.1 You can then move 'mf2pt1.1' into '/usr/man/man1' or any other man page directory. Note that the 'mf2pt1' man page is fairly rudimentary. It @@ -233,9 +232,9 @@ new fonts designed with 'mf2pt1' in mind, but it is unlikely that entirely from closed paths, using Metafont's *fill* and *unfill* commands. ('mf2pt1' has limited support for *draw* and *undraw*, but their use is currently discouraged. *filldraw* and *unfilldraw* issue a -warning message and invoke *draw* and *undraw*, respectively.) The Type 1 -format requires that these paths be nonoverlapping. The following are -some of the alternatives for removing path overlaps: +warning message and invoke *draw* and *undraw*, respectively.) The +Type 1 format requires that these paths be nonoverlapping. The +following are some of the alternatives for removing path overlaps: 1. Install FontForge. As part of its final step in producing a Type 1 font, 'mf2pt1' instructs FontForge to replace overlapping paths @@ -243,7 +242,7 @@ some of the alternatives for removing path overlaps: 2. Remove overlaps using Metafont code within the font program itself. A '.zip' file attachment to a 6 January 2005 article - (http://tug.org/mailman/htdig/metapost/2005-January/000080.html) by + (https://tug.org/pipermail/metapost/2005-January/000080.html) by Boguslaw Jackowski on the MetaPost mailing list (subject: "Re: all intersections between two paths") includes a MetaPost library which assists with that task. The library provides a *find_outlines* @@ -365,10 +364,12 @@ do not need to be enveloped within a test for 'ps_output'. *font_unique_id* The unique ID for this font. The ID should be between 0 and - 16,777,215. If not specified, 'mf2pt1' will choose an ID at random - from the "open" range, 4,000,000-4,999,999. All IDs not in that - range are allocated by contacting Adobe's UniqueID Coordinator. (I - don't believe a fee is involved, but I don't know for sure.) + 16,777,215, with the "open" range being 4,000,000-4,999,999. All + IDs not in that range are allocated by contacting Adobe's UniqueID + Coordinator. (I don't believe a fee is involved, but I don't know + for sure.) If a unique ID is not specified, 'mf2pt1' will not + write a unique ID to the file. Note that Adobe no longer + recommends including unique IDs in fonts. *font_version* The version number of the font. This should be of the form @@ -431,9 +432,9 @@ parameters listed in *note Parameters::. *font_coding_scheme* *string* '"standard"' -*font_comment* *string* '"Font converted to Type 1 - by mf2pt1, written by - Scott Pakin."' +*font_comment* *string* '"Font converted to + Type 1 by mf2pt1, written + by Scott Pakin."' *font_family* *string* (The value of *font_identifier*) @@ -479,7 +480,7 @@ parameters that 'mf2pt1' accepts: if known ps_output: font_coding_scheme "ot1"; - font_comment "Copyright (C) 2014 Scott Pakin."; + font_comment "Copyright (C) 2020 Scott Pakin."; font_family "Kerplotz"; font_fixed_pitch false; font_identifier "Kerplotz Light Oblique"; @@ -503,7 +504,7 @@ Adobe, it's generally better not to assign *font_unique_id*; let The same parameters can also be specified on the command line as follows: - mf2pt1 --encoding=ot1 --comment="Copyright (C) 2014 Scott Pakin." + mf2pt1 --encoding=ot1 --comment="Copyright (C) 2020 Scott Pakin." --family=Kerplotz --nofixedpitch --fullname="Kerplotz Light Oblique" --name=Kerplotz-LightOblique --designsize=10 --italicangle=-9.5 --underpos=-100 --underthick=50 --uniqueid=4112233 --version=002.005 @@ -617,10 +618,11 @@ a--largely useless nowadays--EBCDIC font encoding: therefore must be prefixed with a slash. Unnamed characters such as control characters are commonly named '_aNUMBER', where NUMBER is the decimal offset into the character table. Undefined characters are -indicated by '.notdef'. In the EBCDIC example, the character at position 0 -in the font will be named 'a0'; the character at position 1 will be -named 'a1'; the character at position 74 will be named 'bracketleft'; -the character at position 129 will be named 'a'; and so forth. +indicated by '.notdef'. In the EBCDIC example, the character at +position 0 in the font will be named 'a0'; the character at position 1 +will be named 'a1'; the character at position 74 will be named +'bracketleft'; the character at position 129 will be named 'a'; and so +forth. Individual characters can be mapped to an encoding either numerically or by executing a *glyph_name* command within a character definition. @@ -663,9 +665,9 @@ File: mf2pt1.info, Node: Future Work, Next: Acknowledgments, Prev: Usage, Up 3 Future Work ************* -One avenue for future work is to enable the font designer to specify Type 1 -font hints directly in the Metafont font program. Hinting is a way for -a font designer to specify how a font should be rendered at low +One avenue for future work is to enable the font designer to specify +Type 1 font hints directly in the Metafont font program. Hinting is a +way for a font designer to specify how a font should be rendered at low resolutions, for example, at typical monitor resolutions. In Metafont, this is done by controlling the way that points are mapped to pixel locations, using commands such as *define_corrected_pixels*, @@ -712,36 +714,41 @@ listed in *note Additional command-line options::; for fixing some code-generation bugs in 'mf2pt1'; for finding a more robust way to dump 'mf2pt1.mem'; for directing me to the overlap-removal code mentioned in *note Restrictions::; for supplying the _crossproduct_, _makeline_, and -_is_clockwise_ functions used by 'mf2pt1.mp'; for proposing the '--bpppix' -command-line option; and, for suggesting various features and +_is_clockwise_ functions used by 'mf2pt1.mp'; for proposing the +'--bpppix' command-line option; and for suggesting various features and improvements to 'mf2pt1'. Thanks also go to Werner Lemberg and Boguslaw Jackowski for updating the *is_clockwise* function in 'mf2pt1.mp' to work around a bug in MetaPost which relates to the *turningnumber* command. Finally, thanks go to Ralf Stubner for providing the T1 encoding vector and for pointing out a typo in the generated font -programs; to Michael Zedler for alerting me to problems with '--encoding' -and suggesting I modify that option to accept PostScript '.enc' files; -and to Michael Ummels for fixing a couple of bugs that made character -widths in the generated fonts slightly too large. +programs; to Michael Zedler for alerting me to problems with +'--encoding' and suggesting I modify that option to accept PostScript +'.enc' files; and to Michael Ummels for fixing a couple of bugs that +made character widths in the generated fonts slightly too large.  Tag Table: -Node: Top623 -Node: Introduction1161 -Node: Requirements2994 -Node: Installation4742 -Node: Usage6555 -Node: Restrictions8271 -Node: Font information10652 -Node: Parameters12010 -Node: Command-line equivalents15374 -Node: Default values16855 -Node: Parameter example19075 -Node: Additional command-line options21084 -Node: Custom font encodings23424 -Node: Restoring mfplain defaults26874 -Node: Future Work27733 -Node: Acknowledgments29597 +Node: Top628 +Node: Introduction1166 +Node: Requirements2998 +Node: Installation4731 +Node: Usage6546 +Node: Restrictions8262 +Node: Font information10640 +Node: Parameters11998 +Node: Command-line equivalents15473 +Node: Default values16954 +Node: Parameter example19174 +Node: Additional command-line options21183 +Node: Custom font encodings23523 +Node: Restoring mfplain defaults26973 +Node: Future Work27832 +Node: Acknowledgments29696  End Tag Table + + +Local Variables: +coding: utf-8 +End: -- cgit v1.2.3