- Compile fixes for OSes that do not declare a function.
- t1asm, t1disasm: More security fixes.
- t1disasm: More security fixes reported by Jakub Wilk and Niels Thykier.
- t1disasm: Security fixes for buffer overrun reported by Jakub Wilk and Niels Thykier.
- t1disasm: Fix an infinite loop on some fonts reported by Niels Thykier.
- t1asm: Use a dynamically allocated buffer to handle huge characters (reported by Werner Lemberg).
- Several minor cleanups.
- Don't use "getline" as a symbol (reported by Karl Berry and C.M. Connelly).
- Add
--enable-multiplatform
(requested by Karl Berry).
- Several minor cleanups.
- t1disasm: Avoid memory corruption bug (strings passed to
eexec_line
are not null terminated). Reported by Werner Lemberg.
- All: Support fonts where the eexec-encrypted portion is binary, and the first ciphertext byte is 0. Reported by Werner Lemberg.
- All: Support fonts, such as those in PostScript files printed by
acroread, where
currentfile eexec
is not followed by a newline.
- t1disasm: Support odd fonts where a character is defined on the "/CharStrings" line. Reported by Werner Lemberg.
- Address build problems reported by Nelson H.F. Beebe.
- t1ascii: Add optional warning when output lines are longer than 255 characters. Requested by Werner Lemberg [email protected].
- t1mac: Fix buglet (C++ comment, and temporary file left behind). Reported by Vladimir Volovich [email protected].
- t1asm: Beware extra characters after
currentfile closefile
. Reported by Luc Devroye [email protected].
- Fixed compilation bugs on various platforms reported by Nelson H. F. Beebe [email protected].
- Fixed Macintosh file bugs: the MacBinary CRC was calculated incorrectly, and extended finder flags were set to random values in BinHex output. Reported, and patch provided, by Tom Kacvinsky [email protected].
- Fixed bug on processing PFA fonts with DOS line endings. The symptom was
t1binary producing strange/unusable fonts. Problem: the all-zeros line,
which signals the end of the font's binary section, was not being
recognized because of an extra
\r
. This has been a bug since version 1.13 -- chagrin! Problem reported by Han The Thanh [email protected].
- t1ascii, t1asm, t1unmac: Raised minimum PFA line length to 8. The Adobe spec may imply that there cannot be whitespace within the first 8 bytes of an ASCII-encoded eexec section; it's somewhat ambiguous. Reported by Rainer Menzner [email protected].
- t1asm: Fixed bug where
t1asm -a
would give a “warning: line length raised to 4” error message. Reported by Tom Kacvinsky [email protected].
-
t1mac: Generated Macintosh fonts now use a custom-drawn icon set, rather than Adobe's default. They also have a t1utils-specific creator signature (T1UT), and their file information mentions t1utils.
-
t1mac: Added the
--filename
option.
- t1mac: Fixed bug where generated files appeared corrupted to Macintoshes. Reported by Marten Thavenius [email protected].
-
Added new program,
t1mac
, which translates PFA or PFB fonts into Macintosh-style fonts. T1mac can output in MacBinary, AppleSingle, AppleDouble, or BinHex format. Suggested by Marten Thavenius [email protected]. -
t1unmac: Added support for BinHex.
-
t1unmac: Fixed bugs in manual page and program options.
- t1unmac: Supports AppleSingle and AppleDouble files with the
--applesingle/double
option. Requested by Kent Boortz [email protected].
-
t1ascii, t1binary, and t1disasm: Fixed bad error message.
-
t1unmac: Generates PFB fonts by default.
- t1asm: Version 1.13 produced complete crap output. My test cases were too limited to catch this. Found by Rainer Menzner [email protected].
-
t1disasm: Complete rewrite. It now uses t1lib.c functions; the goal is to handle PFA and PFB fonts consistently. This has been extensively tested, but there may be bugs.
-
t1disasm, t1asm: Fixed to support fonts with multiple Subrs and CharStrings sections, like some old Oblique fonts.
-
PFA minimum line length raised to 4.
-
t1ascii, t1binary, t1disasm: Changes in t1lib.c to support reading binary PFA fonts. Requested by Tom Kacvinsky [email protected].
-
t1ascii, t1binary, t1asm, t1disasm: Support fonts with whitespace following the
currentfile eexec
line. Embedded fonts in PostScript generated by Acrobat Reader have this property. Reported by Tom Kacvinsky [email protected]. -
t1ascii, t1asm, t1unmac: Use lowercase hex digits instead of uppercase.
-
t1unmac: Added
--line-length
option for PFA output.
-
Bug fix in t1asm/t1disasm: if a
readhexstring
procedure was defined, we got confused. Reported by Luc Devroye [email protected]. -
t1binary now has a maximum block length of 2^32 - 1. "Feature" requested by Werner Lemberg [email protected].
-
t1ascii and t1binary each accept both PFA and PFB fonts. If you pass an ASCII font (PFA) to t1ascii, it will output it mostly unchanged, and similarly for PFB fonts and t1binary. The
-l
options will still take effect, so you can uset1ascii -l 60
to shorten the encrypted line lengths of a PFA font. t1ascii also does some newline translation (changes carriage returns to newlines).
- t1asm: Fixed bug when
-l
option wasn't provided. Caught by Giuseppe Ghibò [email protected].
-
t1asm/t1disasm: Provide support for Type1C (Compact Font Format) font files. These fonts have unencrypted character strings, signalled by a negative lenIV value. Suggestion and patch thanks to Tom Kacvinsky [email protected].
-
t1ascii/t1asm: Added
-l/--line-length
option to control maximum encrypted line length. Suggestion thanks to Giuseppe Ghibò [email protected].
- t1asm/t1disasm: Be more robust on fonts that don't end in
mark currentfile closefile
. John Vromans [email protected] provided a font that ended withmark
on one line andcurrentfile closefile
on another; t1asm and t1disasm did not recognize the encrypted section of the font had ended, and generated some garbage.
-
Added some more Type 2 commands (flex, flex1, hflex, hflex1) from a revision of the Type 2 spec. (I wouldn't have known about this except for CurveSoft's revised t1utils package, available at http://www.curvesoft.com. These t1utils are more up-to-date than theirs, however.)
-
t1asm: Fixed one Type 2 command's translation (cntrmask was incorrectly mapped to 18, not 20).
- Integrated patches from Jan-Jaap van der Heijden [email protected] to support building t1utils under 32-bit Windows.
- The t1utils package now uses automake.
-
t1asm: Should now work with fonts that have no /Subrs sections. Previously, assembling such a font would silently fail; all the character definitions would be mistaken for procedures and t1asm wouldn't translate them. Problem noticed and fix suggested by Tom Kacvinsky [email protected].
-
t1disasm: Removed spurious debugging output and improved warning message about unknown charstring commands.
-
Changed fgetc/fputc into getc/putc.
-
--help
now prints to stdout, following the GNU Coding Standards. -
Makefiles: Added
make uninstall
target, enabled./configure
's program name transformations, made VPATH builds possible.
- t1asm/t1disasm: Changed unknown charstring commands at the request of Werner Lemberg and LEE Chun-Yu. An unknown escape in the charstring, like 12 X, is translated to "escape_X" rather than "UNKNOWN_12_X".
-
t1unmac did not actually understand the
-r
and-b
options. Fixed. -
t1unmac: Added better diagnostics to help you diagnose seeking problems.
-
Initial release with Eddie Kohler as maintainer.
-
All: Updated to the GNU program behavior standards (long options,
--help
,--version
). Banners removed. Added more error messages. -
t1binary: Removed fixed limit on line length.
-
t1binary: Supports Macintosh files, whose lines end in
\r
. -
t1binary: Supports an odd number of hex digits in a line.
-
t1asm/t1disasm: Added support for Type 2 commands like
blend
andadd
, which also appear in some multiple master fonts like Adobe Jenson. -
t1asm/t1disasm: Added support for unknown charstring commands. t1disasm translates an unknown command #X to "UNKNOWN_X", and t1asm does the reverse.
-
t1asm/t1unmac: Changed default output to PFB.
-
t1unmac: Used to be called
unpost
.t1unmac
is a much better name.