Some "right" points on diagonal stems could be incorrectly identified as
"left", and vice versa.

There was a typo in UnitCloserToHV(), which resulted into a wrong unit
vector being sometimes preferred.

Some stems may mark more than one ball terminal, and those ball terminals
may depend from different "base" stems. Attempt to take care of this.
Autoinstructor: patch from Alexey to fix bugs reported by Andrey V. Panov:
- RP1 was not set correctly after MDRP'ing first edge of dependent stems.
- Vertical stems with no snappable points at left edge were improperly handled.
- Use new FPGM 16, 17, 18 instead of 1, 11, 12 on 'control counters' enabled.
- Now off-curve points can be used as dstem key points.
- Use ALIGNRP instead of MDRP to place points at dstem edges if possible.
- Some dstems benefit from NOT trying to maintain the slope.
Autoinstructor: patch from Alexey:
- Fix an issue reported by Andrey V. Panov (counter control again).
- One type of dependent stems were positioned with wrong method;
  resulting in serifs pushed beyond their blue zones and other quirks.
Add support for reading/writing version 1.8 of Adobe's feature file format
(while, I hope, retaining the ability to read version 1.6). Fix a number
of bugs in parsing feature files.

FontForge now supports the 'BASE' table (in feature files).

The new format is considerably better than the old and can now be used to
express almost all of OpenType.

Changes:
  * ability to name anchors and value records and use them later.
  * contourpoints used to be expressed as "<contourpoint 2>" and are
      now expressed as "contourpoint 2" (no brokets). Adobe does not
      mention this in the changelog.
      [Incompatible change]
  * It is now possible to specify a GDEF mark attachment class in the
      lookupflags statement.
  * The syntax for mark to base/ligature/mark lookups is completely
      different.
      [Incompatible change]
  * The syntax for contextual lookups has been extended to allow them
      to reference lookups by name.
      [FontForge has always done this. When I suggested to Adobe that
       they follow suit they said they would not. They have now followed
       suit but have used an incompatible syntax to accomplish the same
       ends. So this is an
       Incompatible change
       for FontForge]
   * The syntax for contextual lookups has been extended to allow for
       the new mark lookups.
   * It is now possible to specify a reverse chaining substitution
       lookup.
   * It is now possible to specify descriptive names for the ss00-ss99
       features.
       FontForge doesn't support this but will parse and ignore it

There are some ambiguities in the spec, however
 * In section 4.d we are told that MarkAttachmentType/UseMarkFilteringSet
  both take <glyph class name>s, yet in 9.b we are told they take
  <mark class name>s
 * In 6.e a NULL anchor is defined by <anchorNULL>, shouldn't this be
  <anchor NULL>? In that same example the NULL anchor is not followed by
  a mark keyword and class, is this correct syntax?
suport for the JSTF table.

new sfd syntax.
Oops. I broke contextual ligatures in feature file parsing.
Patch by Alexey Kryukov to support composites (references) in bitmap fonts.
Document the user visible changes of Alexey's bitmap reference patch.
Document support for the Justify table.
Update for new feature file format.
The transform function from the fontview (and python) would transform images in the background layer multiple times -- once for each selected layer.
Barry points out a free which is sometimes inappropriate.
Create faked HV stems for corner points at the ends of diagonal stems when
preparing data for the autoinstructor.
Autoinstructor: patch from Alexey:
- More tweaking to diagonal stems.
- Added support to horizontal ghost hints
  not tied to blue zones and vertical ghost hints.
Autoinstructor: fixed a hang reported by Andrey V. Panov.
FontForge was supposed to check that the compile time (include file) freetype library version number matched the installed version number. But it didn't. Only matters in the debugger, but is important there.
Metrics view had problems with cid fonts.
Oops. Remove debug print statement.
The regen bitmaps dlg sometimes did not use freetype for all glyphs.
Some inconsistancies in ff python docs and reality.