Log message:
Massive cleanup of buildlink3.mk and builtin.mk files in pkgsrc.
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.

Log message:
Changes 20050502:
* Bug fixes

Log message:
Remove USE_GNU_TOOLS and replace with the correct USE_TOOLS definitions:

	USE_GNU_TOOLS	-> USE_TOOLS
	awk		-> gawk
	m4		-> gm4
	make		-> gmake
	sed		-> gsed
	yacc		-> bison

Log message:
Remove USE_BUILDLINK3 and NO_BUILDLINK; these are no longer used.

Log message:
Changes 20050310:
* Deleting a glyph class within a kerning by classes object caused a crash
* Added some support for palm bitmap fonts
* Replace with reference only replaced the first instance.
* The Options dlg behaved oddly with respect to Apple & OpenType modes
* When given a glyph with conflicting hints for which the first contour
  contained no hints, then in type2 output the glyph was drawn at a strange
  offset from its correct position.
* When generating an opentype font from a script, and specifying flags,
  the round coordinates flag was ignored
* When generating a font from a script using the default flag setting,
  we would always generate afm/tfm/pfm files
* KANOU pointed out that the stroked font import glyph command only worked
  if multilayer set.
* Added a preview bitmap to eps files.
* In a bitmap only font the font metrics menu items behaved in unexpected ways
  (as if they referred to a postscript font rather than the bitmap fonts)
* Various fixes to make importing stroked eps files into stroked fonts work
  better.
* KANOU requests a preference item to turn off use of freetype in font view.
* Fix more rounding errors in remove overlap.
* Fix some problems in the routine which finds roots of an arbetrary quartic.
* The remove bump option of simplify could screw up memory.
* Remove overlap got unhappy about control points which caused a very tiny
  overlap between adjacent splines
* Redo from the fontview usually caused a crash.
* KANOU provides a MakeLine scripting command
* If TYPE3 (multilayer) was not enabled, there was a flow of control through
  a function which did not return anything.
* Recovery files did not contain multilayer marks which lead to strange
  behaviour and crashes
* Converting a font to multilayer caused a crash if there were outline glyph
  windows open.
* Make the encoding for scripts be utf8 consistently
* Allow the scripting Export command to take a format spec
* Add support for reals to the scripting language
* NearlyHv{Cps,Lines} scripting commands erroneously complained about
  too many args
* ff had a bug when outputting otf contextual ligatures
* Fix various crashes and infinite loops involved in parsing bad font files.
* ff had problems with user defined encodings.
* Made ff work if the psuedo-type "real" was defined to be a double.
* the string += concattonation operator in scripting screwed up memory
* Problems with -c <arg> syntax
* The font type detector could fail to notice an svg file as such
  if it began with a byte order character.
* Ord didn't do proper type checking on its second argument

Log message:
Add RMD160 digests to the SHA1 ones.

Log message:
Changes 9-Feb-2005:
* Use freetype's FT_Outline_Get_Bitmap to make freetype rasterize from our \ 
internal data structures. Use freetype by default for the fontview and \ 
metricsview (except in some cases).
* The bitmap dlg didn't work for multilayered fonts when told to use freetype to \ 
rasterize.
* If we had a contour nested inside another, and did an Overlap Exclude with the \ 
nested contour selected, then that contour was not excluded.
* The []Correct Direction check box when importing PostScript, didn't do \ 
anything. (or rather it did, but got overrulled later)
* In bitmap only fonts, bitmaps created without moving the width line would get lost.
* Added a scripting command "SelectByColor"
* Don't apply transformations to glyphs which aren't worth outputting
* Moving control points with the get point info command had problems in \ 
quadratic splines.
* When adding type42 support I broke multiple master support.
* Werner provided a patch to add a trailing newline to my type1 fonts.
* Support for PaintType==2 and stroked fonts.
* Various problems with the clustering command
* Oops, somehow a patch reverted and things didn't work on systems without iconv
* worked on a couple of other configuration problems for the mac
* Some people install libraries without headers. Be prepared.
* Uniscribe (MS unicode text layout routines) may ignore either the GPOS or the \ 
GSUB table depending on the script, and may even refuse to use the font at all \ 
if it doesn't have the right stuff in GPOS/GSUB. A Hebrew font must have both a \ 
GPOS and a GSUB. If it doesn't the font is not used. A latin font need not have \ 
either, but if it doesn't have GSUB then GPOS won't be used.

Log message:
Changes 20050117:
* CapsLock now makes the arrow keys scroll in the outline view
* We lost count of hints when generating type2 fonts in glyphs with references
  to something containing hints which did not overlap. If we were unlucky,
  <new-cnt+7>/8 was different than <real-cnt+7>/8 and we ended up \ 
with garbage
  in the charstring.
* Add a TeX table to contain TeX metrics.
* TFM output was wrong. the TFtoPL doc says "reencoding with original encoding
  could create a glyph table one too small resulting in writing/reading garbage
  and an eventual crash.
* KANOU fixed a couple of problems in reading glyph names from bdf fonts.
* KANOU needed to disambiguate between "Point" a unit of measurement and
  "Point" a geometric object.

Log message:
Changes 31-Dec-2004:
* Ah, windows pfm files expect the metrics to be output in win latin encoding
  order, not in the encoding defined by the pfb file. (Actually there are other
  posibilities for encoding, but as none is documented, I must ignore them).
* ReplaceWithReference broke at some point
* Add an argument-pair to the ReplaceWithReference() scripting command to allow
  the user to specify the amount of error that will be accepted.
* When generating a Type1 font, if a glyph had a single reference to a glyph not
  in adobe encoding, and that glyph itself had a single reference (in adobe enc)
  and some splines, then ff would make a reference to the ref in adobe enc and
  ignore the splines.
* Upgrade to Adobe-Japan1-6
* Various fixes to svg output
* Ghost hints could get outside a glyphs bounding box in a type2 font.
* The generated truetype unique id string had an off by one error in the month
* Add support for dashed lines in multilayered mode
* In Full Page Glyph printing, the glyph was offset slightly from where it
  should have been.
* Pasting a reference into a multi-layered font produced a very odd layer
* ff didn't update the metrics view if the user pasted the selection with the
  middle mouse button.
* if a character were not in the current encoding then ff would not display it
  in the metrics view (even if it were in the font)
* Make the behavior of control points at the ends of open paths more reasonable
* The Point->Curve command did not adust control points correctly
* The View->Display Substitutions had numerous problems
* Fix several problems from unicode unification of accents. Many characters
  which are said to be based on cedilla actually use a comma, other characters
  said to be carons also use comma. Make the n-with-apostrophe character be
  treated as an accented letter.
* Werner points out that straight lines should generally not be simplified (as
  they will no longer be straight afterwards). Add this knowledge to the
  simplify command.

Log message:
Bump PKGREVISIONs due to libtiff update.
Some BUILDLINK_RECOMMENDED bumps done also.

(If I missed any, please let me know -- and let me know a good
way to automate this.)