in the process. (More information on tech-pkg.)
Bump PKGREVISION and BUILDLINK_DEPENDS of all packages using libtool and
installing .la files.
Bump PKGREVISION (only) of all packages depending directly on the above
via a buildlink3 include.
All library names listed by *.la files no longer need to be listed
in the PLIST, e.g., instead of:
lib/libfoo.a
lib/libfoo.la
lib/libfoo.so
lib/libfoo.so.0
lib/libfoo.so.0.1
one simply needs:
lib/libfoo.la
and bsd.pkg.mk will automatically ensure that the additional library
names are listed in the installed package +CONTENTS file.
Also make LIBTOOLIZE_PLIST default to "yes".
- Forced PostScript target in the doc directory to file.
- Subsetting code extended in order to ensure that components of
composite characters are also part of the subset.
- Hinting meachanism reworked in order to get rid of some
rasterizing artifacts.
- Experimental support for stroked fonts (PaintType=1)
- Experimental support for stroking standard ATM fonts with PaintType=0.
- Functions for drawing rectangles.
- Bug Fixes
Changes 5.0.1:
- Support for Flex was not adapted to the changes from 5.0.0. This led to
rasterization errors in fonts that use the Flex functionality --> fixed.
- Bug Fixes
have it be automatically included by bsd.pkg.mk if USE_PKGINSTALL is set
to "YES". This enforces the requirement that bsd.pkg.install.mk be
included at the end of a package Makefile. Idea suggested by Julio M.
Merino Vidal <jmmv at menta.net>.
* Move t1lib.config.netbsd sample file to t1lib.config.sample, which is more
OS-neutral.
- Bug fixes.
- Fixed kerning mapping code. Kerning did not work correctly for characters
that appeared multiple times in an encoding vector.
- In the same context a new function, T1_GetEncodingIndices() has been added
to the API. It returns an array of indices (by contrast,
T1_GetEncodingIndex() returns only the lowest index found).
- Support for composite characters.
- Additional support for dvips encoding files (thanks to suggestion and
contribution by Nicolai Langfeldt (janl@linpro.no).
- Global Font Metrics Information is loaded from AFM files in order to be able
to read the typographic ascender. Line ruling did not behave as
documented. However, problems could still exist because the typographic
ascender specification is optional in AFMs.
- Reorganized search path handling and, in particular, the respective
documentation is more detailed.
- The configuration file now allows multiple lines of one type of search path
specification and it is also possible to quote path specification in order
to specify paths that contains special characters like spaces, colons, etc.
- Multiple font databases are supported.
- T1_PrintLog() extended to accept a variable argument list.
- The environment variable T1LIB_LOGMODE is evaluated to give the user the
chance to specify a loglevel and hence to detect t1lib-problems even if the
application programmer did not enable the log file features.
- Color problem in t1x11-module fixed.
- Fixes in AFM parser. Among others, Version had been read as name, instead of
as string. This led to a failure to scan global font info for some standard
AFMs.
