Unescaped left brace in regex is deprecated, passed through in regex; marked by <-- HERE in m/^dup (\d+) { <-- HERE $/ at /usr/bin/mkt1font line 243. Unescaped left brace in regex is deprecated, passed through in regex; marked by <-- HERE in m/^dup \d+ { <-- HERE $/ at /usr/bin/mkt1font line 258. Unescaped left brace in regex is deprecated, passed through in regex; marked by <-- HERE in m/^/([a-zA-Z_][a-zA-Z0-9_.]*|\.notdef|\.null) { <-- HERE $/ at /usr/bin/mkt1font line 272. Unescaped left brace in regex is deprecated, passed through in regex; marked by <-- HERE in m/^/([a-zA-Z_][a-zA-Z0-9_.]*|\.notdef|\.null) { <-- HERE $/ at /usr/bin/mkt1font line 287. Unescaped left brace in regex is deprecated, passed through in regex; marked by <-- HERE in m/(/FontBBox { <-- HERE -?\d+ )-?\d+ -?\d+ -?\d+/ at /usr/bin/mkt1font line 552. /usr/bin/mkt1font version [unknown] calling Getopt::Std::getopts (version 1.11 [paranoid]), running under Perl version 5.22.1. [Now continuing due to backward compatibility and excessive paranoia. See 'perldoc Getopt::Std' about $Getopt::Std::STANDARD_HELP_VERSION.] Syntax: mkt1font -n fontname -d definition-file -a afm-file -f font-file [-s shrink-factor] [-c candrabindu-adjustment] [-b] Mkt1font creates new Type 1 PostScript fonts based on existing fonts ("input fonts"). In order to do this it makes use of I. Lee Hetherington's programs t1asm and t1disasm, which must be present on the system. A successful run will generate an AFM file and a PFB file, as well as a DIS file containing a disassembled version of the PFB file (including useful comments). Four options must be specified on the command line, as follows: -n should name the font it is intended to generate. Avoid names such as "myfont", as both mkt1font and other programs attempt to draw conclusions from the name; better would be something like "Utopia_French-BoldItalic". The generated font files will also use this for their basename. -d should refer to a font definition file. This file (which could usefully be named, e.g., "French.def") should consist of lines of character definitions, in the form "number" "character" or "number" "character" "accent" Here "number" represents the character's position in the new encoding and may be expressed in decimal, octal or hex; "character" names the character (e.g. "comma", "eight", "A") or consists of the word ".notdef" (indicating that the specified number's "slot" in the new encoding is to be empty); and "accent" optionally names an accent to be placed on the character. In addition to the standard accents available in PostScript fonts, "underbar" and "underdot" are also available, as are "under" versions of all the normal superscript accents ("underdieresis", "underring", etc.). The Indian accent "candrabindu" may also be specified: it is formed by overprinting a breve with a dotaccent. Finally, "overdot" may be used as a synonym for "dotaccent". If the character named in the "accent" position is not in fact a valid accent character, the program interprets the definition as a request for a digraph formed from the "character" and the "accent". A digraph consisting of, say, "k" and "h" will be indistinguishable from the letters "k" and "h" printed consecutively, but the digraph "kh" can itself receive accents like any other character: see next paragraph. A new character (such as "amacron" or "kh") may be freely used in the "character" position of a further definition (such as "amacron breve" or "kh underbar"). There is no constraint on the ordering of definitions within a definition file. The definition of "a macron" does not have to precede that of "amacron breve": requests for "impossible" characters are deferred until their constituents have had a chance to come into being. "Slots" for which no new definition is given retain the definition they have in the input font. The definition file may also contain blank lines and comments (introduced by "#"). -a should refer to the AFM (Adobe Font Metrics) file for the input font. -f should refer to the binary font file (PFB) for the input font. (In fact the equivalent ASCII file (PFA) is also acceptable for input, but the output font is always in PFB format.) -s may optionally give the factor, expressed as a per-thousand value, by which normally superscript accents (such as dieresis, ring) should be shrunk when they are used as subscript accents (such as underdieresis, underring). Values of around 800 may be found useful. -c may optionally give two comma-separated numerical values to adjust the x and y coordinates of the dotaccent placed within a breve to form the candrabindu accent. -b may optionally be specified to block the use of predefined accented characters, forcing mkt1font to define its own versions. This may be useful to secure a consistent appearance in cases where a font designer does not share mkt1font's views on where accents should be placed. The -h option prints this help.

Unescaped left brace in regex is deprecated, passed through in regex; marked by <-- HERE in m/^dup (\d+) { <-- HERE $/ at /usr/bin/mkt1font line 243. Unescaped left brace in regex is deprecated, passed through in regex; marked by <-- HERE in m/^dup \d+ { <-- HERE $/ at /usr/bin/mkt1font line 258. Unescaped left brace in regex is deprecated, passed through in regex; marked by <-- HERE in m/^/([a-zA-Z_][a-zA-Z0-9_.]*|\.notdef|\.null) { <-- HERE $/ at /usr/bin/mkt1font line 272. Unescaped left brace in regex is deprecated, passed through in regex; marked by <-- HERE in m/^/([a-zA-Z_][a-zA-Z0-9_.]*|\.notdef|\.null) { <-- HERE $/ at /usr/bin/mkt1font line 287. Unescaped left brace in regex is deprecated, passed through in regex; marked by <-- HERE in m/(/FontBBox { <-- HERE -?\d+ )-?\d+ -?\d+ -?\d+/ at /usr/bin/mkt1font line 552. /usr/bin/mkt1font version [unknown] calling Getopt::Std::getopts (version 1.11 [paranoid]), running under Perl version 5.22.1. Usage: mkt1font [-OPTIONS [-MORE_OPTIONS]] [--] [PROGRAM_ARG1 ...] The following single-character options are accepted: With arguments: -n -d -a -f -c -s Boolean (without arguments): -b -h Options may be merged together. -- stops processing of options. Space is not required between options and their arguments. [Now continuing due to backward compatibility and excessive paranoia. See 'perldoc Getopt::Std' about $Getopt::Std::STANDARD_HELP_VERSION.] Syntax: mkt1font -n fontname -d definition-file -a afm-file -f font-file [-s shrink-factor] [-c candrabindu-adjustment] [-b] Mkt1font creates new Type 1 PostScript fonts based on existing fonts ("input fonts"). In order to do this it makes use of I. Lee Hetherington's programs t1asm and t1disasm, which must be present on the system. A successful run will generate an AFM file and a PFB file, as well as a DIS file containing a disassembled version of the PFB file (including useful comments). Four options must be specified on the command line, as follows: -n should name the font it is intended to generate. Avoid names such as "myfont", as both mkt1font and other programs attempt to draw conclusions from the name; better would be something like "Utopia_French-BoldItalic". The generated font files will also use this for their basename. -d should refer to a font definition file. This file (which could usefully be named, e.g., "French.def") should consist of lines of character definitions, in the form "number" "character" or "number" "character" "accent" Here "number" represents the character's position in the new encoding and may be expressed in decimal, octal or hex; "character" names the character (e.g. "comma", "eight", "A") or consists of the word ".notdef" (indicating that the specified number's "slot" in the new encoding is to be empty); and "accent" optionally names an accent to be placed on the character. In addition to the standard accents available in PostScript fonts, "underbar" and "underdot" are also available, as are "under" versions of all the normal superscript accents ("underdieresis", "underring", etc.). The Indian accent "candrabindu" may also be specified: it is formed by overprinting a breve with a dotaccent. Finally, "overdot" may be used as a synonym for "dotaccent". If the character named in the "accent" position is not in fact a valid accent character, the program interprets the definition as a request for a digraph formed from the "character" and the "accent". A digraph consisting of, say, "k" and "h" will be indistinguishable from the letters "k" and "h" printed consecutively, but the digraph "kh" can itself receive accents like any other character: see next paragraph. A new character (such as "amacron" or "kh") may be freely used in the "character" position of a further definition (such as "amacron breve" or "kh underbar"). There is no constraint on the ordering of definitions within a definition file. The definition of "a macron" does not have to precede that of "amacron breve": requests for "impossible" characters are deferred until their constituents have had a chance to come into being. "Slots" for which no new definition is given retain the definition they have in the input font. The definition file may also contain blank lines and comments (introduced by "#"). -a should refer to the AFM (Adobe Font Metrics) file for the input font. -f should refer to the binary font file (PFB) for the input font. (In fact the equivalent ASCII file (PFA) is also acceptable for input, but the output font is always in PFB format.) -s may optionally give the factor, expressed as a per-thousand value, by which normally superscript accents (such as dieresis, ring) should be shrunk when they are used as subscript accents (such as underdieresis, underring). Values of around 800 may be found useful. -c may optionally give two comma-separated numerical values to adjust the x and y coordinates of the dotaccent placed within a breve to form the candrabindu accent. -b may optionally be specified to block the use of predefined accented characters, forcing mkt1font to define its own versions. This may be useful to secure a consistent appearance in cases where a font designer does not share mkt1font's views on where accents should be placed. The -h option prints this help.