- Check against MultipleMasterFonts somewhat more tolerant, so that
Type 1 Fonts automatically created from Multiple Master Fonts (e.g.
using Mmpfb) should now be acceptable.
- The configure-machinery had been somewhat out of date and has been
updated. The distributed configure script has been generated by
AutoConf 2.59 and the redistributed libtool parts are taken from
GNU libtool 1.5.10.
- Top-Level TeX-file in the doc subdirectory adapted to recent TeX
systems' requirements.
- Added IsoLatin9.enc to distribution.
- Subsetting extended so that it works for SEAC-constructed composites
even if no AFM composite character information is available
- Somewhat more intelligent defaults for subsetting when composite
characters are included in the subset.
- Reallocation had been broken by relocation of internal StandardEncoding
vector. This problem turned out on systems where realloc() actually
returned a different pointer.
- Fix for outline code on 64bit systems. This involves a redefinition
of the T1_PATHPOINT struct. This should be uncritical because for 32bit
systems there is no difference, whereas on 64bit systems, this has never
worked correctly before.
- DESTDIR support in Makefile.in by Volker Zell
- Support for XLFD font database format (in which the fonts' names appear
in the first place on a line).
- Further Bug Fixes
should automatically pull in libXpm when -lXaw is given, but it doesn't
seem to work correctly on Darwin. Modify the xglyph Makefile so that
we explicitly link in -lXpm when we link against -lXaw. This should
fix the problem noted on Darwin in the bulk builds. Bump the PKGREVISION
to 4.
Several changes are involved since they are all interrelated. These
changes affect about 1000 files.
The first major change is rewriting bsd.builtin.mk as well as all of
the builtin.mk files to follow the new example in bsd.builtin.mk.
The loop to include all of the builtin.mk files needed by the package
is moved from bsd.builtin.mk and into bsd.buildlink3.mk. bsd.builtin.mk
is now included by each of the individual builtin.mk files and provides
some common logic for all of the builtin.mk files. Currently, this
includes the computation for whether the native or pkgsrc version of
the package is preferred. This causes USE_BUILTIN.* to be correctly
set when one builtin.mk file includes another.
The second major change is teach the builtin.mk files to consider
files under ${LOCALBASE} to be from pkgsrc-controlled packages. Most
of the builtin.mk files test for the presence of built-in software by
checking for the existence of certain files, e.g. <pthread.h>, and we
now assume that if that file is under ${LOCALBASE}, then it must be
from pkgsrc. This modification is a nod toward LOCALBASE=/usr. The
exceptions to this new check are the X11 distribution packages, which
are handled specially as noted below.
The third major change is providing builtin.mk and version.mk files
for each of the X11 distribution packages in pkgsrc. The builtin.mk
file can detect whether the native X11 distribution is the same as
the one provided by pkgsrc, and the version.mk file computes the
version of the X11 distribution package, whether it's built-in or not.
The fourth major change is that the buildlink3.mk files for X11 packages
that install parts which are part of X11 distribution packages, e.g.
Xpm, Xcursor, etc., now use imake to query the X11 distribution for
whether the software is already provided by the X11 distribution.
This is more accurate than grepping for a symbol name in the imake
config files. Using imake required sprinkling various builtin-imake.mk
helper files into pkgsrc directories. These files are used as input
to imake since imake can't use stdin for that purpose.
The fifth major change is in how packages note that they use X11.
Instead of setting USE_X11, package Makefiles should now include
x11.buildlink3.mk instead. This causes the X11 package buildlink3
and builtin logic to be executed at the correct place for buildlink3.mk
and builtin.mk files that previously set USE_X11, and fixes packages
that relied on buildlink3.mk files to implicitly note that X11 is
needed. Package buildlink3.mk should also include x11.buildlink3.mk
when linking against the package libraries requires also linking
against the X11 libraries. Where it was obvious, redundant inclusions
of x11.buildlink3.mk have been removed.
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.
