oldchangelog.html | searchcode

/htdocs/oldchangelog.html

https://bitbucket.org/sortsmill/sortsmill-tools
HTML | 9713 lines | 8104 code | 1606 blank | 3 comment | 0 complexity | c47053390f6c3ff3ae2659190a9bd4b7 MD5 | raw file
Possible License(s): GPL-3.0, LGPL-2.0

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">

<html xmlns="http://www.w3.org/1999/xhtml">
<head>
  <meta name="generator" content=
  "HTML Tidy for Linux (vers 25 March 2009), see www.w3.org" />
  <!-- Created with AOLpress/2.0 -->
  <!-- AP: Created on: 16-Sep-2001 -->
  <!-- AP: Last modified: 29-Apr-2010 -->

  <title>Older changes to FontForge</title>
  <link rel="icon" href="fftype16.png" />
  <link rel="stylesheet" type="text/css" href="FontForge.css" />
  <style type="text/css">
/*<![CDATA[*/
  p.c3 {text-align: center}
  span.c2 {color: red}
  p.c1 {text-align: right}
  /*]]>*/
  </style>
</head>

<body>
  <div id="in">
    <table align="right">
      <tr>
        <td>
          <blockquote id="lit">
            <b><small>CHAPLAIN:</small></b><br />
            &nbsp;It was very interesting; I was dreaming I
            stood<br />
            &nbsp;On Jacob's ladder, waiting for the gates to
            open.<br />
            &nbsp;And the ladder was made entirely of diminished
            sevenths.<br />
            &nbsp;I was surprised, but not put out. Nothing<br />
            &nbsp;Is altogether what we suppose it to be.

            <p class="c1"><i>The Lady's not for Burning</i><br />
            Christopher Fry</p>
          </blockquote>
        </td>
      </tr>
    </table>

    <p><a href="changelog.html">Current changes</a><br />
    <a href="pfaeditchangelog.html">Changes to PfaEdit (predecessor
    to FontForge)</a><br />
    Changes to the <a href="sfdchangelog.html">sfd format</a>.</p>

    <ul>
      <li>24-August-2008

        <ul>
          <li>
            <table align="left">
              <tr>
                <td><img src="FF32.png" width="32" height=
                "32" /></td>

                <td><img src="FFsfd32.png" width="32" height=
                "32" /></td>
              </tr>
            </table>

            <p>Changes to create a stub Mac application. Add an
            apple event handler to fontforge so that it will notice
            when the finder wants it to open files. Add icons, etc.
            so it will look like a mac app.</p>
          </li>

          <li>Make it possible to drag and drop lookups

            <ul>
              <li>from one font info window to another<br />
              &nbsp; &nbsp; (copy lookups from one font to
              another)</li>

              <li>within a font info window<br />
              &nbsp; &nbsp; (reorder lookups)</li>
            </ul>
          </li>

          <li>Layers can now be marked as either background or
          foreground.

            <ul>
              <li>Foreground layers may be generated into
              fonts</li>

              <li>Background layers may contain images. Pasting
              into an empty glyph in a background layer will not
              set the width. Splines in background layers do not
              make a glyph worth outputting.</li>
            </ul>
          </li>

          <li>Add a color picker so users can select glyph label
          colors other than red, cyan, green, etc.</li>

          <li>Memory problems with references, introduced recently,
          have been fixed.</li>

          <li>I hope I'm now getting keysyms right for non-latin
          menu short cuts.</li>

          <li>Typo in background layer patch could cause a crash in
          fonts with many layers.</li>

          <li>Werner wants an $iscid variable to determine whether
          a font is a cid-keyed font or not.</li>

          <li>add font.iscid to python too.</li>

          <li>python font.cid* variables didn't work, fix
          them.</li>

          <li>Add $haspython variable to normal scripting so I can
          detect if python is available.</li>

          <li>When pasting a reference into an order2 layer, ff
          would sometimes miss the fact that the instructions were
          out of date.</li>

          <li>Replace with references had the same problem.</li>

          <li>In scripting, instructions did not get checked for
          up-to-dateness</li>

          <li>In the charview, unlink ref only worked on the
          foreground layer.</li>

          <li>Patch by Barry (fixed up by me) to fix up open
          charviews when a layer is added.</li>

          <li>Barry points out that Contour.round and Layer.round
          are supposed to have an optional argument, but instead
          have a required arg.</li>

          <li>Just as pasting references screws up instructions, so
          does replace with reference. Do the same thing that we
          just did to rplref.</li>

          <li>When scripting without a UI, the char changed routine
          did not check to see if it should clear the instructions
          on a change. It now does.</li>

          <li>Setting device table adjustments from the accent pane
          of the Math dlg didn't work.</li>

          <li>File-&gt;Revert File (from the UI) didn't work.</li>

          <li>If a contextual chaining pos/sub in a sfd file
          referred to a non-existant lookup we would insert a NULL
          lookup into a rule. This would cause almost anything that
          used that lookup to crash. Now, simply remove the
          sequence/lookup info.</li>

          <li>When importing lookups we might import a lookup twice
          if it were nested.</li>

          <li>When generating bitmaps automatically from a script
          it was possible that the freetype library got initialized
          too late and we'd pass a NULL pointer to FT_Memory_Face
          -- and things would crash.</li>

          <li>In a quadratic layer of a glyph, when selecting an
          on-curve point and trying to make it interpolated, if
          that point had no control points then behavior was
          odd.</li>

          <li>didn't create an input context for top level window
          char and font views. This meant could only use ASCII in
          menus if the focus were in the top level window (in the
          scroll bars, or the menu bar.</li>

          <li>Typo in the code to display side bearings in the
          charview.</li>

          <li>FontForge assumed that all anchor classes for a given
          subtable were in sequence, but Panov has a font where an
          anchor class for a different subtable appears in the
          middle of a list of classes for the desired subtable.
          Result was garbage output, and View-&gt;Show Att
          crashed.</li>

          <li>View-&gt;Next/Prev [Def] &amp; Find In Font View
          don't work in charviews when there are tabs active.</li>

          <li>R. Sander points out that if you select an ordered
          set of lookups in one font and import them into another
          they become disordered. Not good.</li>

          <li>When pasting into a charview we only set the width if
          there was nothing in foreground. When pasting into the
          fontview we always set the width because we were clearing
          the foreground before we pasted (unless we did paste into
          -- then we didn't set the width).

            <p>With layers that should all change. We should only
            set the width if there is nothing in any of the
            potential foreground layers. Don't count the background
            layers or the grid psuedo layer. Don't count open
            contours (might be a secondary guide line layer or
            something). If we're going to clear a layer before
            pasting (normal behavior in fontview) then don't count
            the layer cleared.</p>
          </li>

          <li>Add several different behavior patterms for the
          metrics view. Users complain that the current
          multi-functional window is confusing and would prefer a
          view which only does kerning, or only sets the advance
          widths, etc.</li>

          <li>Due to a typo, merging two splinesets at a curve
          point generally left the point marked with default
          adjustment enabled on its control points.</li>

          <li>Another layers problem. Only in the foreground layer
          could anchor points be moved.</li>

          <li>Python glyph.unlinkReference command didn't
          work.</li>

          <li>My intent was that ligature carets positioned at 0
          didn't count (0 isn't meaningful -- a ligature with a
          zero-width first component?) but that only got
          implemented for 'lcar' table not for 'GDEF'. So fix that.

            <p>Also allow the user to specify exactly how many
            ligature carets s/he wants rather than just setting a
            minimum bound.</p>

            <p>Also 'lcar' (Apple) output was broken.</p>

            <p>Also neither AAT nor OpenType supports negative lig
            carets, so if the user drags a lig caret line negative,
            have it stick at 0.</p>
          </li>

          <li>Moving ligature carets always marked for an undo in
          the foreground layer. Register the movement in the layer
          in which it happens.</li>

          <li>When placing an accent glyph about which we know
          nothing, assume it should be centered on top.</li>

          <li>Change sfd.c so that it will treat the sequence
          "backslash newline" as no characters on input (er, except
          in ASCII85 input). And so that it thinks it can parse
          version 4 or the sfd format.

            <p>We don't generate version 4 yet, and we won't for a
            while. Version 4 will include the ability to insert
            backslash newline into long lines. This is so we can
            conform to the internet requirements of fewer than 990
            bytes on a line. And the delay is so that people don't
            scream at me for making an incompatible change to the
            format -- if I give the parser time to perculate
            through the user community, with luck no one will even
            notice -- especially as long lines are rare.</p>
          </li>

          <li>Selections/Clipboard didn't work in textfields on
          64bit intel. There seems to be a bug in the 64bit Xlib
          which doesn't transfer 32 bit quantities properly. I was
          passing unicode strings as 32bit UCS4, but UTF8 will work
          just fine instead.</li>

          <li>Add the ability to clear all device tables associated
          with a kerning by classes table. (Needed because of a bug
          which introduced garbage).</li>

          <li>We didn't think we could read in a kerning subtable
          (class or pair) with device tables, so we converted them
          to pst data. We can read them in in optimized form and we
          should do so.</li>

          <li>Alexej points out that if a glyph has
          "instructions_out_of_date" set on it, then setting the
          instructions via a script should clear the bit -- but
          didn't.</li>

          <li>Werner points out that if a type2 charstring
          contained a sequence &lt;num&gt; endchar then ff would
          set the width of the charater even if the the width had
          already been set. Width can only be set on first stack
          clearing operation, any extra params on subsequent calls
          get ignored.

            <p>Actually it's worse than that, the spec says that if
            there are too many things on the stack then start
            parsing the stack from the unexpected end.</p>

            <p>Adobe have admitted that the obvious reading of
            their spec is incorrect (they can't quite bring
            themselves to say the spec is wrong). So revert some of
            the way we were parsing type2 charstrings.</p>
          </li>

          <li>Barry complains that when building ff does not apply
          the ".cap" suffix when using inverted breve.</li>

          <li>Valgrind finds a bug in drawing non-BMP characters in
          the metrics view.</li>

          <li>Alexej would like to be able to manipulate
          non-unicode glyphs with the text field of the metrics
          view. The textfield used to map all non-unicode code
          points to 0xfffd, but if the font doesn't make use of the
          supplementary private use areas (planes 15&amp;16) then
          create a mapping from the font into these areas so that
          we can represent non-unicode glyphs as funky private use
          glyphs.

            <p>(Only do this if font doesn't use these areas).</p>
          </li>

          <li>Alexej points out that in non-foreground quadratic
          fonts the "Points-&gt;Dont Interpolate" command doesn't
          do anything.

            <p>Fix a couple of other foreground specific things
            too.</p>
          </li>

          <li>Barry points out that setting a glyph's anchorPoints
          from python does not mark a glyph as changed nor force an
          update.</li>

          <li>Autoinstructor: large patch from Alexey:

            <ul>
              <li>handlles conflicting H/V stems much better;</li>

              <li>tries to place HStems between blues better;</li>

              <li>adds optional apparatus for instructing
              serifs;</li>

              <li>relies on generic point-to-stem snapping routines
              from stemdb.c;</li>

              <li>needs FPGM changed (older FF's glyph programs
              should still work, but FPGMs need updating!).</li>
            </ul>
          </li>

          <li>If the user has opened a backup sfd file (one that
          ends in .sfd~) and does a save on it, then pop up a save
          as dlg instead of blindly saving it. Saving it back to
          the backup is probably wrong, yet saving it onto the
          non-backup version without prompting the user is
          questionable.</li>

          <li>glyph.appendAccents didn't mark the glyph as changed
          nor did it force an update.</li>

          <li>Barry wants a way to control the use_my_metrics bit
          of a reference from python.<br />
          Give him a hack<br />
          glyph.useRefsMetrics(name[,set])</li>

          <li>Add a glyph.appendAccent() command.</li>

          <li>Ralf from end-if.de points out that when trying to
          change the kerning between two glyphs which have a kern
          class setting of 0, then ff keeps asking the same
          question several times before a non-zero value is
          entered. (once when the field is clicked in, once when a
          minus sign is typed, and once more when a number is
          entered).</li>

          <li>The python stuff won't compile under cygwin because
          it used pointers to stuff in shared libraries as
          initializers of static variables. It seems windows can't
          handle that. This patch should provide a work
          around.</li>

          <li>Add a font.importLookups (from another font) function
          to python scripting.</li>

          <li>When joining two splinesets (during glyph editing) we
          didn't pay attention to any user settings for the control
          points, and we'd just always refigure default control
          points. Now use user specified directions when
          possible.</li>

          <li>Add a problem (Find Problems) which will look through
          all glyphs for those with both contours and references,
          and which will create a new glyph to contain the contours
          and make a reference to it in the original.

            <p>Do something similar for bad transformation matrices
            (those with members 2 or more (or less than -2)).</p>
          </li>

          <li>Importing a kerning class from one font to another
          (and perhaps merging fonts) could cause memory problems
          if the number of second classes were bigger than the
          number of first classes.</li>

          <li>Retain sizes of bitmap and metrics views. People seem
          to like this even if I don't.</li>

          <li>Still problems with the guide lines layer

            <ol>
              <li>Displaying a point read bad memory (probably
              harmless, might cause visual artifacts).</li>

              <li>Edit-&gt;Undo in guide layer trampled
              memory.</li>
            </ol>
          </li>

          <li>Find Problems would occasionally pop up a blank
          problem dlg.</li>

          <li>Only show points of inflection in the active
          layer.</li>

          <li>If a glyph window were displaying something other
          than the foreground layer then changes in that window
          would not be reflected in dependant glyph windows (a
          change to tilde didn't show in atilde) nor in the
          fontview.</li>

          <li>In a cubic glyph with references, turning on point
          numbering did not renumber the references. They seem to
          be numbered for TrueType. Not sure where that comes
          from.</li>

          <li>Alexey points out that after deleting the active
          layer, ff does not update the internal bitmap font it
          used to display glyphs in the font view.</li>

          <li>Make "-lang ff" work for "-lang=ff", it's more
          consistent with the rest of the arguments.</li>

          <li>Add a -unique argument which means that FF checks to
          see if another fontforge is running on the current
          screen. If no other fontforge exists things proceed
          normally, but if there is another, then we send it our
          arguments and ask it to open them, and then we exit.</li>

          <li>Make the OFLib dialog have an option to download a
          preview when you click on a line (rather than requiring
          you press the [Preview] button for each).</li>

          <li>The BitmapsAvail and BitmapsRegen scripting functions
          were broken by the layers patch (they generated bitmaps
          of whatever was in the background layer).</li>

          <li>Put in some checks to warn the user when a 'kern'
          table subtable uses more than 10920 pairs.</li>

          <li>Give the user one of those "This operation cannot be
          undone" warnings when deleting a layer in Font Info.
          (Similar warning about instructions if user changes last
          quadratic layer(s) to cubic without deleting any).</li>

          <li>When deleting the last quadratic layer, delete the tt
          instructions also.</li>

          <li>When deleting a layer from a font, ff very carefully
          went through all open glyph views to make sure none was
          looking at the layer being deleted (and fixing them up if
          they were) -- but it totally ignored the font views.
          Their layers needed to be updated too. And the metrics
          views.</li>

          <li>The Import menu item in Font Info-&gt;Lookups popup
          menu was always enabled. It should not have been.</li>

          <li>Add menu items in Font Info-&gt;Lookups (popup menu)
          to do a global add/remove language from a specified
          script in all selected lookups.</li>

          <li>Get Info (maybe a few other things) didn't work on a
          selected reference which wasn't in the foreground
          layer.</li>

          <li>Copy/Paste of references only worked well in
          foreground layer.</li>

          <li>Only in the foreground layer was it possible to
          select a reference by clicking on it.</li>

          <li>Snapping to blues was broken due to a typo in the
          code.</li>

          <li>Still were a number of places where behavior depended
          on the spline order in the foreground layer:

            <ul>
              <li>Could only debug a glyph if the foreground layer
              were quadratic</li>

              <li>Show gridfit used some point numbers from the
              foreground layer and some from the layer being
              shown.</li>

              <li>Gridfit didn't change when changing layers.</li>
            </ul>
          </li>

          <li>Peter Lunicks points out that a tooltip in the prefs
          dlg actually was for a different preference item.</li>
        </ul>
      </li>

      <li>20-July-2008

        <ul>
          <li>Updated Russian UI</li>

          <li>Updated Simplified Chinese UI</li>

          <li>Small Caps dialog greatly rewritten and merged into
          the sub/superscript dialog and a new change glyph
          dialog.</li>

          <li>Alexey Kryukov makes Small Caps and friends deal with
          diagonal stems.</li>

          <li>Update the upload mechanism to OFLib to send a
          preview image, license text (if specified in our
          database) and fontlog (again, if in our database).
          Currently OFLib throws away both the license info and the
          fontlog, but I hope they will fix that in time.</li>

          <li>Add a dialog to browse fonts on the OFLib.</li>

          <li>Fix some bugs in feature file generation of
          contextual chaining lookups which refer to marks. Note
          these are not supported in the spec. This is a FontForge
          only extension.</li>

          <li>If a script contain no default language features (but
          did contain some languages) then ff produced a garbage
          script table for GPOS/GSUB.</li>

          <li>A number of Dialogs still did not autosize themselves
          for different languages Create Hints, Kern (Anchor) Pair,
          Review Hints.</li>

          <li>Still places where ff uses the foreground layer
          rather than the current layer to determine if a glyph is
          quadratic.</li>

          <li>On systems using different font metrics, the debug
          pane looks bad with the buttons partly covered by the
          instruction pane. If the font is large, and the cvt dlg
          empty, then I'm told ff complains.</li>

          <li>Barry points out that Add Encoding Slots scrolls to
          the wrong place.</li>

          <li>Adding glyphs in compacted encodings caused
          problems.</li>

          <li>When the user resizes the outline glyph window,
          retain that size and use it for the default size of
          subsequent invocations of the window.</li>

          <li>It used to be that whenever ff opened an sfd file
          then all subsequent new fonts (or fonts opened from real
          font files) would be displayed in windows the same size
          as the one requested in the sfd file. Only set the window
          size preference when the user explicitly changes it, not
          upon openning something with a different setting.</li>

          <li>In a CID-keyed font, when opening an empty CID slot,
          ff could trample memory.</li>

          <li>BlueFuzz support for autohinter and metafont.</li>

          <li>Add some checks to make sure that we can survive bad
          font data without crashing.</li>

          <li>When trying to change kerning between the last two
          glyphs in the metrics view using the text field (rather
          than dragging the line) then the textfield would change,
          but the kerning would not.</li>

          <li>In the metrics view, give the user several options
          about the grid (which shows the advance widths of the
          glyphs)

            <ul>
              <li>hidden</li>

              <li>fully displayed</li>

              <li>small lines at the top and bottom of the
              pane</li>

              <li>fully displayed except when the user is adjusting
              kerning or the advance width, etc. When adjusting
              grid vanishes until user releases the mouse
              button.</li>
            </ul>

            <p>(setting is sticky).</p>
          </li>

          <li>Allow the user to customize the colors in the metrics
          view.</li>

          <li>In the metrics view (or in the print display dlg)
          when glyphs are overlapping (e asier to see when glyphs
          are large) then the places where one glyph ends and
          another begins often have a faint halo of lighter pixels.
          Try to improve things and make these joins be more
          uniform in color.</li>

          <li>Add minimal support for alpha channels (treat them as
          a bitmask for transparent).</li>

          <li>I find it really hard to believe that this is an
          error, but I have a second hand report that MicroSoft
          claims that it is. To me making it erroneous is pointless
          and annoying, but I don't write the spec.<br />
          Add to Find Problems and Validate a check to see that if
          a base glyph (or mark) contains an anchor point in one
          anchor class in a lookup subtable, then it must have
          anchor points for ALL anchor classes in that
          subtable.</li>

          <li>Fontimage would crash if asked to process a font with
          glyphs not in BMP. Make fontimage better about fonts
          which contain no standard scripts (Apostolos's Phaistos
          font).</li>

          <li>A few tweaks to make stemdb.c usable for resizing
          glyphs and stem control.</li>

          <li>When importing lookups into a font, append the
          fontname to the lookup name only if there is already a
          lookup in the new font with the original name.</li>

          <li>Empty glyphs containing a "." in the name could cause
          ff to crash when doing or checking to see if it could do
          a build accented.</li>

          <li>Gasp editing was broken (still) from the change to
          the cleartype stuff.</li>

          <li>Andrey P. would like to see a reference's bounding
          box in the Element-&gt;Get Info dlg for the
          reference.</li>

          <li>Revert glyph had some stray memory references.</li>

          <li>Add two proposed language tags for IPA use (one for
          IPA and one for Americanist).</li>

          <li>In an empty python layer layer.boundingBox should
          return a tuple of 4 zeros, instead it returned a tuple of
          2 zeros and 2 random garbage values.</li>

          <li>Validate dlg's scrollbar was broken, and you couldn't
          drag the thumb up to the top (you could get it to the top
          by other ways).</li>

          <li>Add a revalidate all menu item to the window to force
          a reevaluation of the entire font.</li>

          <li>Add ability to import graphics from a page of a pdf
          file.</li>

          <li>Python interface does not categorize points.</li>

          <li>The (python) psMat.skew command skewed vertically,
          rather than horizontally and by the wrong amoung.</li>

          <li>When doing a font sample from a script which did not
          set the page width/height explicitly, then ff would use a
          size of 0 for each. All text drawn was out of the imaging
          area, lines were too short (as well as invisible), too
          many pages (all blank).</li>

          <li>Barry points out that "print" is a python keyword. So
          font.print() doesn't work. Call it printSample()
          instead.</li>

          <li>Freetype now (or in the next release, 2.3.7) supports
          dropout modes, which means fontforge must do a bit of
          work when generating rasters for the debugger.</li>

          <li>Move some logic out of fontimage.pe and into
          fontforge to make a default string for a font image more
          widely available.</li>

          <li>When saving an image fromt the print dlg, the top
          line was off the top of the image.</li>

          <li>Interpolated points need not be on integral
          boundaries, but ff was checking for them. Different
          problems in validator and find problems, but both
          wrong.</li>

          <li>In the point near hint check (find problems), ff was
          leaving the hint selected.</li>

          <li>Fix some rounding errors in spline/line
          intersection.</li>

          <li>in Font Info, after user pressed [OK] FF set the
          state of the subscript superscript default checkbox to
          the panose default checkbox by mistake. This means if the
          user defined panose and not sub/super garbage would
          appear in the OS/2 sub/super fields.</li>

          <li>fontimage didn't get the script right, so features
          weren't applied properly.</li>

          <li>More work on conflicting stems.</li>

          <li>Pressing [Done] in the print dialog would right to a
          random address on the stack. Depending on what was going
          on when this was done it could cause a crash.</li>

          <li>Fix an uninitialized variable introduced by the last
          change to order2 conversion.</li>

          <li>Add the ability to open an archive and peek inside it
          for fonts. Useful if we want to open stuff from the open
          font library which is often packaged in zip files.</li>

          <li>Add a new validation check to see if a glyph has
          non-integral coordinates. Only an error in TrueType (and
          can't happen when fontlinting a truetype file, but could
          happen on an sfd file). Add some logic to ask user if
          they intend to generate truetype in cases where we aren't
          sure.</li>

          <li>Add a preference which allows people to change the
          pixmap dir -- and do what we can to reload images from
          the new dir. Some old windows may not be updated, but new
          ones should reflect the new stuff.</li>

          <li>When ff changed the name of a glyph, it fixed up all
          the tabs in charviews to the new name -- but in neglected
          to refresh them. So they still showed on the screen with
          the old name (until something forced a refresh).</li>

          <li>The Anchor Class dialog (which lists all anchor
          classes of a subtable) only let you create an Anchor
          Control dialog for the first anchor class.</li>

          <li>Guard (harder) against generating pathological
          results when converting cubic to quadratic splines.</li>

          <li>If we had a spline which almost doubled back on
          itself, sufficiently so that the spline intersector found
          lots of really close points, which it called
          intersections, but not sufficiently so that our collinear
          detector caught it, then we'd generate a ton of
          intersections, overflow certain arrays, and trash the
          stack. =&gt; ff would crash. I didn't think this could
          happen, until someone provided a test case, so put in
          guards against this.</li>

          <li>provide python access to

            <blockquote>
              glyph.altuni
            </blockquote>

            <p>either None, or a tuple of tuples, one sub-tuple for
            each alternate. each sub-tuple is (alternate-unicode,
            variation selector (or -1), reserved for future=0
            now).</p>
          </li>

          <li>Trying to build dieresis with "PreferSpacingAccents"
          set meant that we tried to build it out of itself, and
          crashed.</li>

          <li>Also fix so that 0x22EF (ellipsis variant) is built
          out of centered dot in a spacing mode, while Ldot uses it
          in a non-spacing mode.</li>

          <li>Merge fonts broken again. This time references didn't
          work.</li>

          <li>Provide a mechanism for loading image files to make
          menu item icons (instead of expecting the images to live
          in memory inside of fontforge). Then provide a bunch of
          these icons so the menus will look more interesting.

            <p>Provide some icons</p>

            <p>Also update the install procedure to put them in the
            right place.</p>

            <p>Preference item containing a directory from which to
            read icon files</p>
          </li>

          <li>FF crashed when opening CID keyed fonts with
          compact_on_open set.</li>

          <li>If fontforge got an end of file in the middle of
          reading a (corrupt) cff font, then ff would sit there
          reading endlessly and ignoring the error.</li>

          <li>Off by one error in drawing the large "pixel"
          rectangles that show grid fit generated.</li>

          <li>Werner points out that my instruction glosses are out
          of date:

            <ol>
              <li>Was following Apple's docs for SCANTYPE, not MS.
              MS has a number of new values.</li>

              <li>Was using an old convention for accessing PPEM
              which broke after freetype 2.3.5</li>

              <li>Added the FreeType return for GETINFO.</li>
            </ol>
          </li>

          <li>Featurefile patch from Barry.</li>

          <li>I used to think that the max glyph instruction length
          field of 'maxp' refered to fpgm and prep. I thought this
          because there was a footnote (which I now see was for a
          different field) saying the field also applied to fpgm
          and prep.</li>
        </ul>
      </li>

      <li>07-June-2008

        <ul>
          <li>New Russian translation of the UI</li>

          <li>Sometimes FF didn't set the message locale directory
          properly.</li>

          <li>Since FF will crash if you load a feature file when
          the Font Info window is open for that font, close the
          Font Info window when loading a feature file.</li>

          <li>New <a href="Styles.html#Italic">dialog</a> to help
          users convert an upright font into an italic one.</li>

          <li>New <a href="Styles.html#Smallcaps">dialog</a> to
          help users create small caps glyphs.</li>

          <li>New <a href="Styles.html#SubSuper">dialog</a> to help
          users create subscript/superscript glyphs.</li>

          <li>And matching python commands: font.italicize(),
          font.addSmallCaps(), layer.stemControl()</li>

          <li>Make it clear that the transform dlg from the
          fontview will move the width of a glyph by default, and
          provide a checkbox so the user can turn this off.</li>

          <li>Fix various bugs in argument handling of
          fontforge.askChoices</li>

          <li>Change font.removeGlyph to accept a single string
          argument to remove the glyph with that name.</li>

          <li>FF didn't like decimal points in the metrics view l/r
          bearing fields -- even though it would put them there
          itself.</li>

          <li>Metrics windows weren't being remetricked after a
          feature file was loaded (nor an afm file for that
          matter). Nor were they remetricked after lookups changed
          in fontinfo.</li>

          <li>Add to python

            <ul>
              <li>font.revert()</li>

              <li>font.revertFromBackup()</li>

              <li>font.buildOrReplaceAALTFeatures()</li>
            </ul>
          </li>

          <li>Changing a glyph's width from a python script didn't
          update the metrics window.</li>

          <li>Adding two languages in the same script to a lookup
          in a feature file didn't work.</li>

          <li>It wasn't possible to rename an anchor class (at
          least not by the obvious method through the dlg).
          Attempting to delete an anchor class popped up an error
          message which didn't provide all its own arguments and so
          could crash on some systems.</li>

          <li>Better error recovery in feature file parsing.</li>

          <li>Werner points out that since I allow the user to see
          points in references transformed to their ultimate
          position, I should also transform the raster.</li>

          <li>Patch by Barry to fix kerning classes (ie. figuring
          out WHAT glyphs go into a class).</li>

          <li>When parsing a feature file which used a default
          languagesystem setup, ff only used the most recent
          script.</li>

          <li>If a lookup contained no data (no subtables, or empty
          subtables) then when generating a feature file ff would
          output stuff to declare a lookup, but when there was no
          content that frame could not be parsed as it would be
          impossible to figure out the lookup type. Try to avoid
          that.</li>

          <li>FF did not put contextual lookups on all the lists
          they needed to be on when loading them from a feature
          file.</li>

          <li>Sometimes the Open Font dlg opened with the files
          shifted left so the first characters of the name were
          outside the window.</li>

          <li>Patch from Barry Schwartz. "include" syntax in
          feature files didn't work.</li>

          <li>Sort button in the lookups pane of font info didn't
          refresh the window after it finished (so things looked
          unsorted even after pressing it).</li>

          <li>When doing a Build Accented on dotted glyphname
          (agrave.sc, etc.) the accent was positioned using anchors
          in the undotted base glyph (a rather than a.sc).</li>

          <li>Fix various problems with tt debugging.</li>

          <li>The XUID and UniqueID fields of a PostScript font are
          deprecated, yet FF has continued to output them by
          default. Make it so FF no longer does so.</li>

          <li>When outputing an sfd file, ff would sometimes output
          a truetype spline as a line if it had a collinear
          control-point. I thought I'd taken care of that, but
          here's another case which needed fixing.</li>

          <li>Typo when loading the underline position field from a
          'post' table. I was subtracting half the underline width.
          I should have been adding it instead. (Why did adobe use
          a different definition of the same concept in two places?
          GRRR).</li>

          <li>It wasn't possible to make the foreground layer
          invisible.</li>

          <li>When the file chooser bookmark list got too long ff
          would crash.</li>

          <li>I wasn't doing the obvious checks to the sfnt header
          in font lint. So now:

            <ol>
              <li>Check that there are no duplicate table
              entries</li>

              <li>Check that there are no overlapping tables</li>

              <li>Check that no tables extend beyond the end of
              file</li>

              <li>Check that the file's checksum is correct</li>

              <li>Check that each table's checksum is correct</li>

              <li>Check that the number of tables is reasonable and
              that the binary search header is consistent with the
              number of tables.</li>

              <li>Check that required tables are present</li>

              <li>Check that certain fixed length tables have the
              correct length.</li>
            </ol>
          </li>

          <li>Werner would like to be able to debug (truetype
          instructions) when using non-square pixels (x_ppem !=
          y_ppem).</li>

          <li>Barry wants to be able to close a tab. Add a menu
          item.</li>

          <li>When a glyph's name changed, I did not update the
          names in any tabs in the charviews -- so those tabs would
          stop working after the change.</li>

          <li>Scrollbar in points debug window wasn't set
          right.</li>

          <li>A. Panov provides a patch. Prefs was losing
          bookmarks.</li>

          <li>the new release of volt reveals some new opentype
          tags.</li>

          <li>If we have a glyph named "agrave.sc" or "eacute.sc"
          then FF will now let you build this as an accented
          character. It will remove the suffix from then name, and
          look up the components of the bare glyph. Then for the
          first component it will search for a glyph named "a.sc"
          and insert it. For the accents it will use "grave.sc" if
          present, and "grave" if it is not.</li>

          <li>FF wasn't handling a FontMatrix in the top dict of a
          cid font.</li>

          <li>Trying to filter for fig files in the Import dlg
          caused a crash.</li>

          <li>Check for bad OS/2 versions (that is, versions
          windows will reject) when loading a font.<br />
          Connect validation's "Points too far" with Find Problem's
          version.<br />
          Make fontlint aware of the new validation states.<br />
          When generating a font we complained about bad os/2
          version only if they asked for a validation. Move it
          somewhere more prominant.</li>

          <li>Add two new problems to find

            <ol>
              <li>Points too far apart</li>

              <li>Bitmap advance width different from scaled
              outline advance widths</li>
            </ol>

            <p>(also boxify the Find Problems dlg).</p>
          </li>

          <li>Add a new validation state: Test that points aren't
          too far appart (must be within 32767 of each other or we
          can't output them).</li>

          <li>Try a little harder to get some of the obscure code
          pages right in the OS/2 table.</li>

          <li>Was getting the first glyph index of OS/2 wrong for
          OTF fonts.</li>

          <li>If an sfnt contains embedded bitmaps, and if those
          bitmaps contain a glyph whose advance width is different
          from that expected by scaling the horizontal advance of
          the vector data, then windows will only get the correct
          metrics if the "Instructions modify width" bit is set in
          the 'head'.flags field.</li>

          <li>If the "changedsincelasthinted" bit got set on a
          glyph by the unlink/remove overlap flag on a glyph during
          font saving, then the glyph did not get restored to its
          original state.</li>

          <li>Doing an Undo in the Guidelines layer didn't work,
          usually crashed.</li>

          <li>Validate didn't work on CID keyed fonts.</li>
        </ul>
      </li>

      <li>29-Apr-2008

        <ul>
          <li>Validate didn't work in CID keyed fonts.</li>

          <li>Pierre Hanser wants an X Resource
          (fontforge.CharView.Rulers.FontSize) to specify the font
          size of text displayed in the info line and the rulers. I
          have applied his patch, but have made no effort to insure
          that text will fit in the space allowed for it.</li>

          <li>Hmm. Freetype seems to dislike rasterizing some
          complex outlines at large pixelsizes in black and white,
          but seems fine with doing them in greyscale.</li>

          <li>When opening a ttc file (and posting a dlg which
          lists all the fonts in the file) try to find a fontname
          in the current locale. We used to look first for English
          and then anything. Now try: First current locale, then
          english, then anything.</li>

          <li>Make the Open Font dlg (and similar file chooser
          dlgs) be customizable, and store that info in prefs.
          Specifically control whether directories are displayed in
          alphabetical order among other files, before normal
          files, or in a separate pane.

            <p>Also add a bookmark (and back/forward)
            mechanism.</p>
          </li>

          <li>Add support for opening a font from http &amp; ftp
          URLs. Can browse ftp URLs, and save fonts back to
          ftp.<br />
          <code>$ fontforge
          http://openfontlibrary.org/people/Nasenbaer/Nasenbaer_-_Widelands.ttf</code></li>

          <li>The validation patch broke the save mac family
          dialog, and then the upload to open font library broke it
          further.</li>

          <li>When doing expand stroke, it is possible to have two
          points so close together that there is no data on the
          curve in between the two. If this happens
          ApproximateFromPointsSlopes can't do a good job. So be
          careful of this case.</li>

          <li>Layers change introduced a potential crash in the
          Embolden command.</li>

          <li>fontimage didn't draw the first line.<br />
          Add a cgi front end to <a href=
          "fontimage.html">fontimage</a> so now it is possible to
          get a font sample of any font on my website.</li>

          <li>In the Display dlg, if you changed the font, or the
          point size without selecting something, then that change
          would vanish instantly. Fix that.

            <p>Also, was a crash bug when mixing a font with a
            baseline table and a font without one (in the disply
            dlg).</p>
          </li>

          <li>Add a command to insert text into a glyph.
          (<code>Element-&gt;Insert Text Outlines)</code> It adds
          the text outlines directly (instead of a draw command
          using another font) because most fonts can't include text
          drawing in their glyphs. Also include a Bind to Path
          variant.</li>

          <li>GLyph lists in kerning classes (in show att) were
          displayed as ligatures.</li>

          <li>Upgrade to unicode 5.1</li>

          <li>If an sfd file were saved with spiros active, and
          then loaded into a version of fontforge without libspiro,
          then bad things would happen. Whenever we check that
          spiros are active also check that they can be active, and
          add some warnings for the user to let him/her know that
          spiros aren't available.</li>

          <li>Add a tile pattern command (if --enable-tile-path)
          this allows the user to replicate any given pattern in
          another glyph.

            <p>This could be used to produce a grid of guidelines,
            or, in conjunction with
            <code>Element-&gt;Overlap-&gt;Intersec</code>t it could
            provide a poor man's "Pattern Fill" (Since Pattern
            fills are only available in type3 fonts this sort of
            makes them work for any font type).</p>
          </li>
        </ul>
      </li>

      <li>30-Mar-2008

        <ul>
          <li>Add support for the OpenType 'BASE' table, and to a
          lesser extent for Apple's 'bsln' table.

            <p>Add python scripting (font.horizontalBaseline,
            font.verticalBaseline) too.</p>

            <p>Add support under Show ATT.</p>

            <p>Remove the old vertical origin field.</p>
          </li>

          <li>Add the ability to create a dummy 'DSIG' table (one
          containing no signatures) so that Windows will show an
          opentype icon for a font with extension 'ttf'</li>

          <li>Add support for gradient and pattern fills to type3
          fonts (only if <code>./configure --enable-type3</code> is
          specified, of course.

            <p>Also add support for cliping paths</p>

            <p>Make fonts containing images work in pdf output.</p>
          </li>

          <li>Bump the sfd version number. This should have
          happened in the last release, but I didn't realize it was
          needed then, thus there will be sfd files with an
          incorrect version number (2) when it should be 3. However
          that should not cause the current parser problems.</li>

          <li>New Greek translation from Apostolos</li>

          <li>Updated Polish translation from Michal</li>

          <li>Apostolos points out that compiling on systems
          without freetype (Solaris boxes) was broken after last
          months layers patch.</li>

          <li>Werner suggested various improvements to Show ATT:

            <ul>
              <li>Lookups should be sorted</li>

              <li>Glyph images should be drawn in more cases
              (before, just for substitutions)</li>
            </ul>
          </li>

          <li>Patch from Alexey, for better handling conflicts
          between diagonal and H/V stems.</li>

          <li>Do a more consistent job of handlong curved stem
          segments. Also collect point data for off-curve points
          too (may be useful in future for TTF hinting).</li>

          <li>Last month I put in a patch to make sure the lsb as
          stored in the 'hmtx' table was really the glyph's lsb if
          bit 1 of the head.flags field were set. Unfortunately I
          read in the lsb as an unsigned number which shifted
          negative lsbs off to around 65535. FF sometimes refused
          to rasterize them. Of course when the font was generated
          they got truncated back to negatives in the output.</li>

          <li>Add a preference item so that fonts will be
          automagically compacted when they are opened.</li>

          <li>Add a new preference item (SeekCharacter) to allow
          users to control which character will be displayed when
          opening a new font. Normally FontForge displays 'A', but
          that's a bit latin-alphabet-centric.</li>

          <li>If palettes were not docked, then a complicated
          series of events could lead to a crash after closing a
          TilePath (Math kerning, Gradient Fill, etc.) dialog.</li>

          <li>Was not outputting the %%LanguageLevel DSC
          comment.</li>

          <li>Generating a CID-keyed otf font was broken by the
          layers patch. (Only the background layer was
          output).</li>

          <li>Encoding-&gt;Add Encoding Slots didn't work for
          CID-keyed fonts.</li>

          <li>Autoinstructor does more consistent vertical stem
          placement for mono and grayscale. Advance width scales
          much better. One downside: letters tend to 'glue' at
          small ppems.</li>

          <li>When FF read in a pairwise positioning lookup with no
          change to the pos of the first glyph, and an x change to
          the second glyph it treated that as a r2l kern pair even
          if the lookup was l2r. This lead to problems.</li>

          <li>In the Print/Display window all vertical GPOS
          positioning was diametrically opposed to the direction it
          should have gone (there was a sign error).</li>

          <li>Print managed to break itself somehow. Print of a
          font display to ps file (or was it pdf) didn't work.
          Type3 pdf fonts were broken, last glyph omitted.</li>

          <li>In the fontview the horizontal advance and baseline
          metrics lines were drawn as if bitmap magnification were
          1 (so if bitmap mag&gt;1 they were in the wrong
          place).</li>

          <li>In the char view, when the active tool is the scale
          tool, show the scale factors on the info line.</li>

          <li>The default set for control points of a corner point
          before/after an hv curve point was to have no control
          point. Make it be the same as a normal curve.</li>

          <li>layers patch broke type3 editing in that: in a type3
          font glyphs don't have the same number of layers so it is
          possible to move from one glyph to another in the char
          view and have the current layer become invalid.</li>
        </ul>
      </li>

      <li>9-Mar-2008

        <ul>
          <li>Undefined value in the martlett patch.</li>

          <li>A variable was placed on the stack in font info which
          needed a longer lifetime. This would probably mean that
          after several remetrickings of that window the jump to
          OS/2 Unicode ranges in the Unicode ranges pane would
          appear in a strange color and oddly shaped. I never saw
          it happen, but it should have. The variable is now
          static.</li>

          <li>When ff read in a contextual subs by glyphs it would
          reorder each glyph list (backtrack, lookahead and normal)
          so that the glyphs were in GID order. So "a b c" would
          probably come out fine in the lookahead list, but would
          be reversed in the backtrack, while "c b a" would be
          reversed in the lookahead). Ug.</li>

          <li>The code which decided on whether to apply a chaining
          lookup approached backtrack data in the wrong order (so
          only lookups with either 0 or 1 backtrack entries worked.
          Which was all I used to test).</li>

          <li>New fonts were created with relative filenames, this
          screwed up some font searches. Make 'em absolute.</li>

          <li>Deleting something in the guidelines layer probably
          caused a crash.</li>
        </ul>
      </li>

      <li>2-Mar-2008

        <ul>
          <li>
            <b><big>Layers</big></b>

            <p>The big change in this release is that every font
            database can now contain multiple layers. Before this
            all layers in a font used the same type of splines and
            there were only 2 or 3 of them.</p>

            <ul>
              <li>Guideline semi-layer -- where all the glyphs of
              the font shared the same set of outlines, to which
              points would snap if desired.</li>

              <li>A background layer -- which could contain
              outlines and also images which could be autotraced
              into the foreground layer.</li>

              <li>A foreground layer -- which was what the font
              really looked like, and what went into generated
              fonts</li>
            </ul>

            <p>Now there may be any number of layers, and each
            layer can contain different types of splines -- so one
            database can contain both quadratic and cubic data and
            can store data for both PostScript and TrueType
            fonts.</p>

            <p>In a normal font all glyphs have the same number of
            layers (this is not true in a type3 font, which each
            glyph may have it's own set of layers). You may set the
            number, names and types of layers width the
            <code>Element-&gt;Font Info-&gt;Layers</code> pane.</p>

            <p>In the font view you can select which layer is
            active (and displayed) with the
            <code>View-&gt;Layers</code> menu item. You can copy
            selected glyphs of one layer to another (automagically
            adjusting the spline type if needed) with
            <code>Edit-&gt;Copy Layer To Layer</code>. You can
            compare to layers for differences with
            <code>Element-&gt;Compare Layers...</code>.</p>

            <p>In the character view the Layers palette has
            changed. The things which controlled the visibility of
            hints have moved to the <code>View-&gt;Show</code> menu
            (as have some other entries that used to be in the top
            level <code>View</code> menu). The layers palette
            solely displays the glyph's layers and controls which
            layer is active.</p>

            <p>The <code>File-&gt;Generate Fonts...</code> dialog
            allows you to specify which layer is to go into the
            font. Note that many things remain common: the hints
            and truetype instructions apply to all layers. GPOS,
            GSUB, kern, and morx information is common all layers.
            The outlines may differ in detail, but outlines from
            which a font will be generated should have the same
            shape.</p>

            <p>Add new python stuff to handle layers:</p>

            <dl>
              <dt>fontforge.activeLayer()</dt>

              <dd>Returns the currently active layer</dd>

              <dt>font.layer_cnt</dt>

              <dd>Returns the number of layers in the font</dd>

              <dt>font.layers</dt>

              <dd>
                A dictionary like object which can be indexed
                either by an integer between 0 (inclusive) and
                layer_cnt (exclusive) or by the name of a layer.
                After indexing it returns a LayerInfo object.
                LayerInfo objects have no independant existance,
                and contain a layer's name and a boolean indicating
                whether the layer is_quadratic.

                <blockquote>
                  <pre>
font.layers[1].name = "Foreground"
font.layers[0].is_quadratic = TRUE
</pre>
                </blockquote>

                <dl>
                  <dt>You may delete a layer</dt>

                  <dd><code>del font.layers["Extra
                  layer"]</code></dd>

                  <dt>You may add a new layer</dt>

                  <dd>
                  <code>font.layers.add("name",is_quadratic)</code></dd>
                </dl>

                <p>(this object has an iterator which returns the
                names of all layers)</p>
              </dd>

              <dt>glyph.layer_cnt</dt>

              <dd>Returns the number of layers in the glyph (this
              is the same as the number in the font, except for
              type3 fonts).</dd>

              <dt>glyph.layers</dt>

              <dd>Returns a dictionary like object which may be
              indexed by layer name or an integer [0,layer_cnt) as
              above. The result is a standard layer object. (this
              object has an iterator which returns the names of all
              layers)</dd>

              <dt>glyph.reflayers</dt>

              <dd>Returns a dictionary like object which may be
              indexed by layer name or an integer [0,layer_cnt) as
              above. The result is a standard list of references.
              (this object has an iterator which returns the names
              of all layers)</dd>

              <dt>layer.export</dt>

              <dd>It is now possible to export the contours of a
              layer (before only glyphs could be exported)</dd>

              <dt>glyph.export</dt>

              <dd>Slight change to the semantics. When outputting
              an outline file, there is now an optional second
              argument which specifies the layer to output. (again
              integer or layer name).</dd>

              <dt>font.generate</dt>

              <dd>Has a new keyword argument "layer" to specify
              which layer should be output.</dd>
            </dl>
          </li>

          <li>M.P. Suzuki requests a way to load the entire 'glyf'
          table of a ttc. Actually he would like to load all 'glyf'
          tables of a ttc, but that would cause all kinds of
          problems (multiple fpgm, prep, maxp, cvt tables, trying
          to fix up GIDs in GPOS/GSUB/kern/* tables, dealing with
          fonts with so many glyphs they could not be generated,
          ...)

            <p>So the command line now takes an --allglyphs
            argument, and the scripting open commands now take a
            value of 4 for the openflags argument to mean this.</p>
          </li>

          <li>Add a command Points-&gt;Make Arc, which is similar
          to Points-&gt;Make Line except that it connects the two
          points with an elliptical arc rather than a straight
          line. The ellipse is choosen to run through the two
          points (obviously) and to be tangent to the slope of
          those points. This isn't enough information to determine
          an ellipse uniquely (three points and two tangents being
          required) so in general there will be an infinite number
          of solutions (and it is possible to provide contradictory
          input so that no ellipse can be found). FontForge may not
          choose the ellipse you had your heart set on. FF will
          first attempt to find an ellipse so that one of the
          points lies on an axis of the ellipse (this will find a
          circle if there is a circle which satisfies the
          constraints above). If that fails it will look more
          generally for ellipses.

            <p>(If you hold down the &lt;Alt&gt; key when you
            select the menu item, FF will leave the ellipse it
            calculated in the background layer. That was a
            debugging technique but I thought it was kind of
            interesting and left it in.)</p>
          </li>

          <li>Further improvements in calculating active zones for
          curved segments for autohinging: if the spline is closer
          to the opposed stem edge at the given point, don't extend
          the active zone any longer.

            <p>If a line's unit vector is close enough to the
            font's italic slant, then prefer the unit vector based
            on the italic slant instead.</p>

            <p>Added an experimental mode which allows to build
            glyph data based on a preexisting hint layout and
            extend it with additional stems.</p>
          </li>

          <li>The rotate tool in char view didn't show the angle of
          rotation.</li>

          <li>Fixed various uninitialized values</li>

          <li>Make sure the first character in marlett is
          0xf020.</li>

          <li>Reinstate the behavior of the symbol encoding that
          the wine developers depend on.</li>

          <li>Add a scripting flag so that script writers can
          control whether a font has a symbol encoding without
          having to use a funky extension. (Wine people don't like
          having to say ".sym.ttf").</li>

          <li>When building a ligature, ff would mark the first
          letter with use_my_metrics. That should only happen when
          building accented glyphs.</li>

          <li>Put in a way for the user to leap easily from Font
          Info-&gt;Unicode Ranges to Font
          Info-&gt;OS/2-&gt;Charsets-&gt;Unicode Ranges.</li>

          <li>python scripting font.sfnt_names would sometimes
          crash.</li>

          <li>When a matrixedit is initialized its last visible
          column (especially if followed by hidden columns) may not
          be at the edge of the matrixedit. This lead to drawing
          spurious lines which annoyed Alexej.</li>

          <li>When running simplify on a quadratic contour and the
          contour doubles back on itself, FF would do an
          optimization which only worked for cubics.</li>

          <li>Werner tells me that if bit 1 of the 'head'.flags
          field is clear then I should adjust so that the left side
          bearing is what is specified in the 'hmtx' table.</li>

          <li>Pdf filter decode didn't work if given an array of
          filters (not even in the array contain only a single
          filter).</li>

          <li>FontForge doesn't support pdf encryption which seems
          to require a license from RSA. Before we'd just announce
          failure for no reason, now announce that the file is
          encrypted and we can't read it.</li>

          <li>Improper test for point matching in references (in
          tt).</li>

          <li>In an un instructed font, the [Default] button in
          FontInfo-&gt;Grid Fitting produces the wrong result (and
          has since I added support for the new gasp features of
          ClearType.</li>

          <li>Doing hint modifications caused errant pointers to be
          used. Often crashing.</li>

          <li>Math strings weren't getting initialized in math
          kern.</li>

          <li>One of the math constants had the wrong friendly
          name.</li>

          <li>Michal points out that tooltips in the math window
          don't get translated.</li>

          <li>TopLeft/TopRight etc. in math kerning weren't
          translated.</li>

          <li>The transform menu item seems to have lost its
          shortcut. Put it back.</li>

          <li>When selecting a control point in the outline view,
          we would always select the next point if both next and
          prev were in the same place (ie, on the base point
          itself). But when the point is at the end of an open
          contour, the one which should be selected is the one
          which controls a spline (which need not be the next
          one).</li>

          <li>Oh dear. My original method for storing background
          layers didn't allow for references (because I didn't put
          them in the background). But I need them now.</li>

          <li>Label some of the horizontal metrics lines</li>

          <li>Trying to move the top accent line resulted in a
          crash.</li>

          <li>Drat. FF really wants to set the latin1 codepage bit,
          even if the user explicitly provides the codepage
          settings. The wine people don't like that.</li>

          <li>If we have two fonts open, a type3 (multilayered) one
          and a normal outline, and we have outline glyph windows
          open from each font, and we move the focus between the
          glyph windows, then the layers palette will get left
          behind when focus moves to the other font. (and other
          more complex senarios when switching between multilayered
          and outline).</li>

          <li>When loading a feature file, ff would complain if a
          mark appeared in two anchor classes -- even if those
          classes were in separate lookups. This meant it got
          unhappy about a mark which was in both a mark 2 mark
          lookup and in a mark to base lookup.</li>

          <li>I had intended not to give warning messages about
          names like "nine.oldstyle" (defined in Adobe's obsolete
          PUA mapping) when loading a tt font, if such a glyph had
          a different unicode mapping (or none) than the one Adobe
          used ages ago. But I screwed up and was generating
          messages anyway.</li>

          <li>When converting cubics to quadratics, if we had a
          curved spline where one of the endpoints of the spline
          had no control point, then we'd get a slope at that point
          of 0/0. This meant that we tried to put a quadratic
          control point on top of that endpoint which looked
          confusing and seemed unnecessary.</li>

          <li>Typo in glyph compare. Caused another crash when
          comparing lookups.</li>

          <li>Didn't handle NULL tokens properly when reading in a
          feature file.</li>

          <li>Make it easier to select control points when the alt
          key is down.</li>

          <li>Add a mechanism for getting default values for
          private dict entries in python scripts.

            <p>(Also provide default values now when [Add]ing
            private entries in Font Info.</p>
          </li>

          <li>Making class0 editable broke the ability to create a
          context chaining class lookup.</li>

          <li>The encapsulation for creating libfontforge broke
          importing a lookup from one font to another.</li>

          <li>Feature file generation omitted a semicolon after
          (some) contextual lookup rules.</li>

          <li>Nasty bug with references in ApplySubstitutions
          scripting command.</li>

          <li>Mark classes didn't work.</li>

          <li>Michal N. points out that "Really Use Typo Metrics"
          should be moved above the typo metrics (or below) but
          should not be in the middle of them.

            <p>He also tells me that the internationalized weight
            classes don't get parsed properly.</p>
          </li>

          <li>Someone handed me a font with a SJIS encoding cmap.
          The cmap mapped a glyph to SJIS 128, which isn't a valid
          SJIS code point. FF got an insane result when trying to
          convert to unicode and crashed. Add a check against bad
          code points.</li>

          <li>Add two proposed features from the pre-draft of OT
          1.6

            <ul>
              <li>Drop Caps</li>

              <li>Character Variants 00-99</li>
            </ul>
          </li>

          <li>Werner wants to be able to select text in the
          warnings window to paste elsewhere. And he points out
          some scrolling flaws as well.</li>

          <li>Could not attach lookups to mac feature
          settings.</li>

          <li>Clean up some display problems in the type3 layers
          palette and layer info dlg.</li>
        </ul>
      </li>

      <li>3-Feb-2008

        <ul>
          <li>New Vietnamese translation from Clytie</li>

          <li>New Russian translation from Alexandre
          Prokoudne.</li>

          <li>New Polish translation from Michal N. .</li>

          <li>FF could crash if a cmap subtable contained invalid
          encoding points.</li>

          <li>Add various new features/scripts/language tags from
          OpenType draft 1.5.</li>

          <li>Add two proposed features from the pre-draft of OT
          1.6

            <ul>
              <li>Drop Caps</li>

              <li>Character Variants 00-99</li>
            </ul>
          </li>

          <li>The warnings window didn't resize properly. It didn't
          let you copy text (ie. a warning) to the clipboard. It
          should have scrolled with keypad keys (arrows, page
          up/down, etc). There should be a way to clear the windows
          so you know that all the warnings are from a given
          operation. Added a popup menu.</li>

          <li>Fixed a problem in the auto hinter.</li>

          <li>Could not attach lookups to mac feature
          settings.</li>

          <li>Clean up some display problems in the type3 layers
          palette and layer info dlg.</li>

          <li>Autoinstructor: turned on strong point interpolation:

            <ul>
              <li>Various important outline points are correctly
              placed between hints' edges.</li>

              <li>Potential benefits for DStem positioning.</li>

              <li>Drawbacks: 2x slower, code generated is now much
              bigger.</li>
            </ul>
          </li>

          <li>The merge (and simplify) command could produce odd
          results if the points surrounding the merge had no
          control points.</li>

          <li>Extend find/replace to handle changing angles.</li>

          <li>The Display/Print dlg would crash when the user
          pressed the reset button if there were at least two
          pointsizes of the font on display. Perhaps in other cases
          too.</li>

          <li>Make shift click in the lookup dialog (but not the
          subtable part) select all lookups between current click
          and a previously selected point.</li>

          <li>glyph.addPosSub doesn't work for ligatures or
          multiple substitutions. It treats both as alternate
          substitutions.</li>

          <li>Michal Now. points out that there are some strings
          not marked for translation in cvruler.c.</li>

          <li>FontForge never checked that fonts had fewer than
          65536 glyphs. I just blythely assumed I wouldn't have to
          worry. Well someone handed me a font with 65731 glyphs,
          and FF treated it as having 195 glyphs. Things got nasty
          after the 196th.</li>

          <li>Fix a crash in autohint.c and an infinite loop in
          stemdb.c.</li>

          <li>Font Compare would crash if one font had a lookup
          subtable which was not in the other.</li>

          <li>Improve the algorithm used to detect reference points
          for stem edges. Enable snapping "corner extrema" to
          predefined hints.</li>

          <li>Remove the obsolete Private Dict to CVT table
          command.</li>

          <li>Michal Now. wants short cuts to change grid fit
          attributes, so a new sub menu with things like increase
          point size, change AA, etc. (with shortcuts, of
          course).</li>

          <li>Patch by Michal Nowakowski. In Show Grid fit not
          setting the mono bit correctly in freetype.</li>

          <li>Bug in pfm file output.</li>

          <li>If we failed to open a plugin library during init, it
          would call LogError before the display was initialized,
          leading to a crash.</li>

          <li>Autoinstructor: If a horizontal stem interpolated
          between blue zones was very close to one of them, it
          often jumped beyond that zone in small ppems. This was
          especcially annoying for serif fonts.</li>

          <li>Improvements (I hope) to the ruler tool

            <ol>
              <li>Make it snap to splines (in addition to
              points)</li>

              <li>Have it draw a line from the start point to the
              mouse</li>

              <li>If they start on a spline, then include info on
              the offset in coordinates parallel to the spline and
              normal to it.</li>

              <li>Provide a "spline length" if the start and end
              points are on the same spline (instead of just if
              they were the end-points of the spline).</li>
            </ol>
          </li>

          <li>In python scripting contour.reverseDirection only
          worked on closed contours.</li>

          <li>If you click wildly in the cvt editor it would
          eventually go into infinite recursion.</li>

          <li>If there were no free anchor class then attempting to
          add an anchor point would pop up the Mark Classes pane of
          Font Info (rather than Lookups). This is sufficiently
          close to Anchor Class as to be very confusing.</li>

          <li>Make label gadgets (and buttons which are also
          labels) handle multiline text.</li>

          <li>If the user closes the font info dlg when there are
          mark class dialogs floating around then close them too
          (there was code which was supposed to do this, but it
          didn't work).</li>

          <li>Try to make it clear in the Mark Classes pane of the
          Font Info that mark classes are not anchor classes.
          Someone got confused...</li>

          <li>Fix some bugs in parsing mark anchors in feature
          files.</li>

          <li>When adding an hvcurve point into an existing spline
          it behaved like a curved point and laid parallel to the
          spline rather than being either horiz or vert.</li>

          <li>FontForge uses floats (which have ~24 bits of
          precision internally) to represent coordinates. Type2
          fonts use a 16.16 fixed notation, which means that we
          only represent coordinates &lt;256 accurately. This will
          cause slight errors during output and input of a font.
          Unfortunately, due to the rel-rel nature of postscript
          these slight errors accumulate.

            <p>So instead, when loading and saving a Type2 font use
            double precision temporaries. This should mean there
            will be no errors to accumulate. There will be slight
            errors when converted to SplinePoints, but these errors
            will not accumulate.</p>
          </li>

          <li>Check several adjacent splines when detecting active
          zones for curved segments and thus make the algorithm
          less dependent from the number of additional points on a
          contour and their exact positions.</li>

          <li>Fix a number of problems that -pedantic complains
          about.</li>

          <li>Some mnemonics in the Element menu are used for two
          items. Clean it up a bit.</li>

          <li>Add a "Find Problems" for non integral coordinates.

            <p>Change the "Ref with bad ttf transformation" so that
            it checks for integral coordinates too.</p>
          </li>

          <li>the glyph.validate function in python was marked as
          taking NOARGS in the method table, but, in fact, does
          take arguments.</li>

          <li>Oops. Validate used to complain if the StemSnap[HV]
          array were missing. But that's perfectly ok.</li>

          <li>Be more lenient when closing a path (when reading in
          a type1/2 font)... we can get rounding errors.</li>

          <li>Add a little LogError to let the user know if there
          are sfnt tables we ignore.</li>

          <li>Deep in the heart of Find Problems check for bad
          contour direction, was a bug where it looked at the wrong
          spline.</li>

          <li>Just as it is possible to have things in 'morx' that
          are not in 'GSUB', it is possible that a 'GPOS' table
          contains no kerning information but a 'kern' table does.
          We used not to read 'kern' if we had 'GPOS', be a little
          subtler and check for the presence of a 'kern' feature
          inside 'GPOS' before deciding whether to read the 'kern'
          table.</li>

          <li>The anchor control dialog didn't work for mark to
          mark anchors when looking at a base mark.</li>

          <li>When a font contained glyphs with multiple encodings,
          then ff would produce bdf files with a char count which
          matched the # glyphs, not the number of encoding slots
          used.</li>

          <li>In a compacted cid font, the status line (containing
          unicode, unicode block/name, etc) was junk.</li>

          <li>Barry wants to be able to mark that it's ok for a
          spline to have intermediate extrema.</li>

          <li>The []TeX Table checkbox was always disabled in the
          save font dlg.</li>

          <li>The DejaVu people want to be able to associate a
          comment with a cvt entry.</li>

          <li>Find Problems-&gt;ATT-&gt;Missing glyph name
          complains about the special string &lt;Delete&gt; which I
          used in Apple lookups to represent the "Delete Glyph"
          action that apple supports and OT does not. Don't
          complain about this any more.

            <p>Add a problem which will look at the glyphs a lookup
            is active for, and then checks the script of each glyph
            against the scripts attached to the features which
            invoke this lookup. If the script doesn't match
            anything, then complain.</p>
          </li>

          <li>If a font contained an empty anchor class (having
          either no base glyphs or no mark glyphs) then when
          dumping out the font subsequent anchor classes got the
          wrong data associated with them.</li>

          <li>Barry wants non-integral hints.</li>

          <li>Barry points out that Scale To Em doesn't scale the
          guidelines.

            <p>Barry also complains that spiro points are rounded.
            This is more debatable. The bezier conversion will put
            bezier points where there were spiros, so if we don't
            round the spiros we get non-integral points. But if we
            do round the spiros we mess up the splines. Hmm.</p>
          </li>

          <li>When complaining about a bad class in a mark (GPOS)
          sub-table, specify the name of the offending mark if we
          can.</li>
        </ul>
      </li>

      <li>10-Jan-2008

        <ul>
          <li>Fixed a crash bug in Auto Hint</li>

          <li>Replaced the Short Cut to AutoInstr</li>

          <li>In Font Info-&gt;Lookups, added to the lookup tooltip
          to show what contextual lookups used the current
          one.</li>
        </ul>
      </li>

      <li>9-Jan-2008

        <ul>
          <li>Fix some problems with AAT. Mutually exclusive
          features in the chain didn't get the right OffFlags set.
          (and didn't work).</li>

          <li>Add DHint support for native &amp; python scripts.
          Prevent users from specifying incorrect unit vectors for
          diagonal hints added via scripts. Also use stemdb.c to
          calculate active zones for normal (horizontal and
          vertical) hints added via scripts.</li>

          <li>Remove my original (and not very good) auto
          instructor. Clean up the docs to remove references to how
          bad it was.</li>

          <li>Add the ability to store a fontlog in the sfd file.
          Available to python scripting. A way to save it to
          FontLog.txt when generating a font. A way to modify it
          before generating. Normal access through Font Info.</li>

          <li>Change the PfEd table so that the font comment is in
          utf8, and the glyph comment subtable too.

            <p>Add subtables to hold:</p>

            <ul>
              <li>Names of lookups and lookup subtables and anchor
              classes</li>

              <li>Guide lines</li>

              <li>Background and spiro layers</li>

              <li>Font Log</li>
            </ul>
          </li>

          <li>It used to be that when a font had both 'mor[tx]' and
          'GSUB' we would only read 'GSUB'. But Michel Boyer wanted
          to read both. So... read 'morx' after 'GSUB' and if we
          find a feature/setting that looks as though it
          corresponds to an existing OpenType lookup (which we can
          convert to a Mac format) then skip that feature/setting,
          presuming it to contain redundant data.

            <p>This is a finer grain approach, but similar to, the
            previous one. There we skipped the whole table,
            presuming it redundant. But in CharisSIL the morx table
            has a lot of functionality orthogonal to GSUB. So we
            must parse both.</p>
          </li>

          <li>The 'feat' table was being output in the wrong order.
          Features were linked together in several ways and 'feat'
          followed the wrong field.</li>

          <li>Two related bugs that Charis SIL invokes:

            <ol>
              <li>This font has a contextual substitution which
              uses class 0 and replaces it via a nested lookup. But
              my feature file output could not handle class 0
              (since it isn't really specified) and would
              crash.</li>

              <li>However, in this case class 0 was specified by
              the coverage table (we fixed that earlier but just
              for kerning classes). So now fix for
              contextuals.</li>
            </ol>
          </li>

          <li>Auto recovery was broken. Ever since I put in the
          code to ask the user what to do with a recovery file (It
          always recovered into a new file).</li>

          <li>When FF opens a char window on my screen it has a bad
          habit of opening it at 40% magnification. Which means
          mouse clicks give things either at em or at half me
          positions. That's bad. Don't want the default behavior to
          create lots of .5 coordinate values.

            <p>Make the window open at 33% instead.</p>
          </li>

          <li>FontForge warns the user when a glyph's name does not
          match its unicode encoding. But in the past it would do
          this for glyphs with multiple encodings even if the name
          matched one of the encodings. Fix that.</li>

          <li>When FF uses doubles internally, it still outputs
          float precision into the sfd file. Fix that.</li>

          <li>Still said "Tangent" rather than "Constraint" in
          points menu when in Spiro mode.</li>

          <li>Ben Laenen of Deja Vu says it would be nice if sfd
          files stored truetype instructions as recognizable text
          rather that squirrily ASCII85 encoded binary data. Sounds
          reasonable. Might as well store 'cvt ' and 'maxp' as
          numbers then.</li>

          <li>Remove some deprecated DStem code. Also move
          CVNumForePointsSelected() to charview.c and make it
          static (not used anywhere else except that file).</li>

          <li>Sometimes the pointers to libspiro didn't get
          initialized.</li>

          <li>If a font had no private dica and one tried to put
          something in it from python, ff would crash.</li>

          <li>Alexej points out that my use of iconv was broken on
          many systems where UCS-4 is big endian on a little-endian
          machine.</li>

          <li>Use freetype to rasterize the fill blit in the char
          view.</li>

          <li>- In search_edge, an array subscript was sometimes
          -1?

            <p>- Previously I forgot to mention Alexey's changes in
            DStems hinting code.</p>
          </li>

          <li>Simple optimization for blue zone hinting - cupped
          serifs should benefit most.</li>

          <li>Update copyright notices. (add 2008)</li>

          <li>Oops, typo in python menu code.</li>

          <li>There is now an incomplete fontforge which uses the
          gtk toolkit.

            <blockquote>
              <pre>
$ ./configure
$ make
$ make install
$ make fontforgegtk
$ make install_gtk
</pre>
            </blockquote>

            <p>About all it can do is open a font and display it.
            If a menu command does not require a dialog then it
            might work. There are probably scores of bugs even in
            the little bit that supposedly does work.</p>

            <p>I think the open dialog is extremely ugly. That's
            not my fault, that's gtk's widget. The open dialog is
            far less functional than the one in the gdraw fontforge
            -- I can't figure out how to enhance it.</p>
          </li>

          <li>Switching to a new internal representation of
          diagonal stem hints.</li>

          <li>Add a mechanism to check that the executable has been
          configured to match the library. And include a library
          date stamp as well as an executable stamp.</li>

          <li>In the metrics view, if I switch from outline view to
          bitmap view (by selecting a strike by pixel size from the
          view menu) then ff would crash.</li>

          <li>Cleanup the library executable interface a bit
          more.</li>

          <li>Minor tweaks to fontview.</li>

          <li>- Alexey suggested improvement for
          HStemGeninst().</li>

          <li>- Added optional experimental code for interpolating
          strong points.</li>

          <li>Barry Schwartz wants to be able to set the "don't
          autohint flag" from python. I'm calling it "manualHints"
          though.</li>

          <li>Barry Schwartz points out that the simplify flag
          "setstarttoextremum" is incorrectly documented. Fix
          that.</li>

          <li>- In HStemGeninst(), new positioning method gives
          bizarre results for overlapping stems. Added fallback to
          old method.</li>

          <li>Make it obvious that the Print/Display dlg HAS a
          menu.</li>

          <li>Crossland wants a way to insert random text into the
          Print/Display dialog. So add the ability to generate a
          bunch of random words that look vaguely reasonable.
          (Invoked by the popup menu in the dlg).</li>

          <li>Exporting spiros to a plate file produced garbage if
          any spiros were selected.</li>

          <li>The Print dlg tended to crash if you did much editing
          in it.</li>

          <li>When switching to spiro mode on an empty glyph (or
          perhaps the first glyph in a new font), FF would
          complain: Internal Error: Character out of bounds in
          bitmap font 0&gt;=0</li>

          <li>Oof. The math stuff doesn't work if device tables are
          disabled. fix it.</li>

          <li>Fix some problems with configuration modes I don't
          use. Correct some pointer arguments which differ in
          signedness.</li>

          <li>If lines are attached to both sides of a diagonal
          stem, then prefer the longer line's unit vector for this
          stem.</li>

          <li>- Fixed snap_to_blues(): it used to mess global
          accuracy setting up.</li>

          <li>- Fixed finish_stem(): it did not mark edges of
          previous hints as done.</li>

          <li>- CHanged HStemGeninst(): it now tries to interpolate
          HStems within blues when possible.</li>

          <li>Dave Crossland points out that ff didn't compile if
          --without-native-script were set.</li>

          <li>Trying to change control points with the point info
          dlg on hv-curve points didn't work.</li>

          <li>Add the ability to insert a list of words into the
          metrics view.</li>
        </ul>
      </li>

      <li>10-Dec-2007

        <ul>
          <li>Redo the internals of fontforge to separate the core
          font engine from its dependance on gdraw, and stuff all
          of that into libfontforge. So libfontforge no longer
          needs gdraw, and can be used to build another user
          interface with a different widget set.

            <p>In theory.</p>
          </li>

          <li>Add the ability to insert a list of words into the
          metrics view.</li>

          <li>If a font has a variant selector 'cmap' subtable, and
          has some unnamed glyphs then base names on the
          information found in the vs subtable as:
          (u0020.vsFE00)</li>

          <li>If a font has a 'MATH' table and some unnamed glyphs
          then try to guess names for glyphs refered to in
          horizontal/vertical glyph construction tables.</li>

          <li>When outputing horizontal glyph variants in the
          'MATH' table I used their vertical size rather than their
          horizontal size.</li>

          <li>Further refinements to the concept of lines: all
          points assigned to the same line now should have filled
          space at the same side. So what we used to call lines
          would be better called edges now. Also the handling of
          bounding box hints has been improved: all relevant points
          are now assigned to a BBox stem hint (not just one point
          from each side).</li>

          <li>Add a user interface to control file recovery (used
          to be only a command line argument).</li>

          <li>Patch by Barry who points out an extraneous line in
          the font iter by search.</li>

          <li>Barry points out that there is a disconnect between
          the docs and the program about the "spiros" member of a
          Contour python object. So correct the docs to read
          "spiros", and change the program so it will accept
          "spiro" as well as "spiros".</li>

          <li>Add the ability to name contours, primarily for
          guidelines.

            <p>Add python support for the contour_name.</p>
          </li>

          <li>Add support for reading Apple's old sfnt wrapped CID
          format (basically the same as the sfnt wrapped 'typ1'
          format.</li>

          <li>FF crashed on Nastaliq Navees from SIL.

            <ol>
              <li>It has no unicode cmap (which ff handled
              incorrectly)</li>

              <li>It has cross-kerning (which ff doesn't handle,
              but still died while explaining that it didn't handle
              it)</li>
            </ol>
          </li>

          <li>Use routines from stemdb.c to generate active zones
          (or stem instances) for manually added hints. The old
          algorithm is still used when reading Type 1/OTF font
          files.</li>

          <li>FontView -&gt; Hints-&gt;Clear hints did not set the
          hints changed bit.</li>

          <li>Erik van Blockland points out that python
          glyph.addPosSub doesn't check for duplicate entries and
          will blindly add something when it should be replacing
          it.</li>

          <li>Also added a short cut so that it is posible to
          specify simple kerning by typing one number rather than
          requiring an additional 7 zeroes.</li>

          <li>Prevent some redundant stem chunks from being
          generated.</li>

          <li>Both Adobe Acrobat and Apple's Preview exhibit what I
          consider to be a bug. According to the PDF reference
          manual, if an Encoding dictionary is not specified for a
          font object then the built in encoding will be used. But
          both these programs reencode to AdobeStandard and do not
          use the font's built in encoding. GhostScript agrees with
          my interpretation and does not reencode.

            <p>However, they ain't gwana change, so I must. Always
            dump out an Encoding dictionary even when it shouldn't
            be needed.</p>
          </li>

          <li>
            <ul>
              <li>Lines are more actively used: stems now have
              'leftline' and 'rightline' properties, and for
              diagonal stems the stem unit vector is always set
              equal to the unit vector of the line corresponding to
              the left edge of the given stem;</li>

              <li>I no longer attempt to calculate "active" zones
              for bounding box hints (they usually don't correspond
              to any actual glyph features and thus look ugly). So
              now only edges of such hints (without any active
              zones) are displayed in the charview;</li>

              <li>diagonal stem detection improved (some checks
              were too strict and actually oriented to HV
              stems);</li>

              <li>the 'blue' property is now used not only for
              ghost hints, but also for regular horizontal stems.
              This may be useful if I ever implement an
              autoinstructor based directly on the stem
              detector;</li>

              <li>glyph data initialization has been separated from
              stem detection and put into a separate routine (a
              first step for unification of algorithms used to
              calculate stem active zones).</li>
            </ul>
          </li>

          <li>When doing a print sample to pdf, the second page
          came out in times bold rather than the user's font.</li>

          <li>I think setting a compact encoding could overflow an
          allocated string array.</li>

          <li>I was setting the Regular bit of OS2.fsSelection if
          the weight class was 400. I probably should have used 500
          instead. Or maybe both. Let's try both for now.</li>

          <li>If a ufo font did not have a lib.plist file (and
          python was enabled) then ff would crash on loading
          it.</li>

          <li>When importing an eps file, ff did not turn off the
          "Bitmap-only" flag. This means that new fonts composed
          entirely of eps files would be treated as bitmap fonts
          (sometimes).</li>

          <li>Moving quadratic control points with the pointer is
          broken (again).</li>

          <li>Metricsview would crash if you deleted a character
          and then clicked in one of it's textfields.</li>

          <li>Fix typo in stemdb.c</li>

          <li>Add a Select-&gt;Open Contours command.</li>

          <li>Add some serbian text (to the built in print
          samples).</li>

          <li>Update the location on the charview info line when
          dragging out a guideline.</li>

          <li>If a glyph had a unicode encoding for one code point,
          and a name which mapped to another, then double clicking
          on the other code point would cause fontforge to provide
          a reference to the base glyphs from the new encoding
          slot. But only in the current encoding map. In other
          words I forgot to set the AltUni field.</li>

          <li>Some people have though winDescent should be a
          negative value for things below the baseline. So make the
          sign of the various descent fields explicit in the
          corresponding popup messages.

            <ul>
              <li>Typo Descent: Negative</li>

              <li>Win Descent: Positive</li>

              <li>Hhea Descent: Negative</li>
            </ul>
          </li>

          <li>If a user edited a glyph in spiro mode, and then did
          something in the fontview ehich caused the spiros to be
          removed (Lots of things: Overlap, Expand Stroke,
          Embolden, ...), and then did a Round to Int (and perhaps
          other things) from the font view, then FontForge would
          crash.

            <p>It expected to find spiros in a glyph marked as
            being edited in spiro mode, and was surprised when none
            were available.</p>
          </li>

          <li>Dave Crossland doesn't like having "..." at the end
          of window titles.</li>

          <li>Back out the Add Extrema in spiro mode patch. Turn
          off display of extrema in spiro mode (and of Points of
          Inflection too).</li>

          <li>Add an autowidth command to the python
          interface.</li>

          <li>contour.lineTo and friends didn't work (didn't
          increment the contour's point count).</li>

          <li>With SnapToInt preference on, and at high
          magnifications, a mouse click would often be snapped so
          that it was well outside the fudge region. This meant
          that clicking on something might not select it.</li>
        </ul>
      </li>

      <li>10-Nov-2007

        <ul>
          <li>Another bug when loading feature files</li>
        </ul>
      </li>

      <li>9-Nov-2007

        <ul>
          <li>Introduced Raph Levien's Spiro curves. Please
          <a href="http://libspiro.sf.net">download
          <b>libspiro</b></a> before using fontforge.</li>

          <li>Deal with things that got deprecated as the mac moved
          from 10.4 to 10.5

            <ul>
              <li>NSAddImage and family have been replaced by
              dlopen</li>

              <li>the old mechanism for referencing a resource fork
              from POSIX "foo/rsrc" has changed to
              "foo/..namedfork/rsrc".</li>
            </ul>

            <p>The new stuff all worked as far back as 10.3 -- but
            FontForge source is no longer compatible with 10.2.</p>
          </li>

          <li>In a truetype font, if a substitution lead to an
          unencoded glyph and the cursor hung over the substitution
          long enough to invoke the popup, then we'd generate a
          tiny font containing just the unencoded glyph, we'd
          complain that there were no encoded glyphs, we'd dismiss
          the popup, we'd generate the glyph image, then we'd try
          to free it with no free function because the popup was
          dismissed.</li>

          <li>Merge Feature File didn't actually merge things in,
          it forgot about existing things -- which caused problems
          for kerning classes which get stored in two lists.</li>

          <li>Allow people to order entries in the PostScript
          Private dictionary (in Font Info)</li>

          <li>Give the user control over how much arrow keys
          accelerate when holding down the Alt (Meta) key.</li>

          <li>People want a Snap To Int preference item.</li>

          <li>Simplify sometimes ignored points.</li>

          <li>People expect to be able to drag guidelines from the
          rulers (because everyone else does that) and don't want
          to bother to learn FF's mechanism. So make that
          possible.</li>

          <li>Dave C wants to be able to use Cntl-Tab to switch
          tabs in the charview.</li>

          <li>If freetype gets a single point open contour in
          postscript mode, it simply skips the contour (does not
          call FT_MoveTo on it). This screwed up my attempt to
          match the results of freetype with the actual splines and
          caused a crash.</li>

          <li>Glyphs with no contours didn't set widthset when read
          from ufo and so were viewed as empty.</li>

          <li>FF was expecting descent to be a positive value in a
          ufo (it is in ArialBlack.ufo), but it seems to be
          negative in most UFOs.</li>

          <li>Erik wants the creation order of contours preserved
          when reading a glif file.</li>

          <li>Oops. glyph/glyphPen types got the wrong names in the
          fontforge python module. (interchanged)</li>

          <li>remove the Elide command. (There's no reason to use
          it, Merge is always better, it just confused people.</li>

          <li>Refrain from simplifying an order2 point where the
          second derivative changes sign.</li>

          <li>If a font has no "fullname" field (and fonts aren't
          required to have one) ff would crash when generating the
          font.</li>

          <li>Ability to Import/Export Raph Levien's plate file
          format.</li>

          <li>If I moved a corner point adjacent to a tangent, the
          slope on the other side of the tangent did not
          change.</li>

          <li>Exporting a glyph to BMP or PNG was broken, probably
          since the addition of python import export filters.</li>

          <li>Add a Strftime scripting command to the legacy
          language.</li>

          <li>Werner points out that I misspelled "persistent" as
          "persistant" in many places, including python member
          names. Correct that. (but leave the old, misspelled
          membernames around but undocumented in case anyone has
          been mislead by my previous documentation.</li>

          <li>Add new python stuff to provide access to
          spiros.<br />
          The fontforge module has a new method -- hasSpiro() which
          returns whether we've got access to libspiro or
          not.<br />
          The module also has a bunch of numeric constants defined
          spiroG4, spiroG2, etc. for use in the<br />
          The Contour type has a new member -- spiros which is a
          tuple of spiro control points (which are themselves
          tuples: x,y,type,flags, where type is one of the numeric
          constants above.</li>

          <li>People would complain that the python interface would
          give them "Invalid second order spline" but no one
          bothered to give me a test case. I hope I've tracked it
          down now.</li>

          <li>Add a "problem" to check for glyphs whose bounding
          boxes are: too tall, too short, too wide, too much to the
          left.</li>

          <li>Used to be I had many problems checked by default.
          Best to turn them all off.</li>

          <li>Oops. FF was using Py_BuildValue("s") on something
          that was already a python string.</li>

          <li>Adam Twardoch suggests that codepoints in the PUA
          have their script determined by their name (rather than
          just returning DFLT). Since Adobe used to put things like
          "a.sc" in this area, that seems a good idea.</li>

          <li>FF marked almost all fonts with the Oblique bit in
          the OS/2 table.</li>

          <li>- Patch from Alexej for his diagonal hinting
          routines, fixes an ugly problem reported by Max
          Rabin.</li>

          <li>Various fixes in stem detection. In particular added
          a concept of "base start" and "base end" for curved
          segments of stem edges, allowing to determine more
          precisely if an active zone (which merges left and right
          segments together) should actually be considered "curved"
          at its</li>

          <li>Make implied points to be ignored when determining a
          diagonal stem validity.</li>

          <li>Swith the timestamps to GMT. Prior to this all
          timestamps have been PS/DT, but now that other people are
          making source changes GMT seems more sensible.</li>

          <li>Max Rabkin supplies a patch to let python import
          plate files.</li>

          <li>A couple of new name table string ids: WWS Family
          &amp; WWS Subfamily.<br />
          Provide reasonable defaults for the wws* ttf names.</li>

          <li>Correct the list of dutch font styles.</li>

          <li>Most of the items in the popup menu of the lookup
          pane didn't work.</li>

          <li>FF wasn't loading python init files from
          ~/.FontForge/python</li>

          <li>When I fixed mark to ligature positioning I broke the
          other three types of anchor positioning (to base, to mark
          &amp; cursive).</li>

          <li>If you pressed the [*] Default check box in the Font
          Info-&gt;OS/2-&gt;Panose area, the values didn't go back
          to the defaults.</li>

          <li>When copying glyphs from one font to another ff would
          sometimes use a temporary value of -2 for the orig_pos.
          This meant that reference fixups didn't work when looking
          at those glyphs.</li>

          <li>Drat. Typo when copying a contextual lookup from one
          font to another caused a crash.</li>

          <li>Add a new point tool which creates curved points
          which are always either horizontally or vertically
          oriented. (I call 'em hvcurves)</li>

          <li>Use ~/.FontForge instead of ~/.PfaEdit</li>

          <li>I'm told there was a typo in my Bulgarian text for
          the Print/Display dlg, and that this should fix it.</li>

          <li>Get some proper Belorussian text.</li>

          <li>Several bugs in my mark attachment routines. There
          was an assumption that only one mark could be attached to
          a base glyph per sub-table. This is wrong for mark to
          base, in that there can be several anchor classes per
          subtable. It is even worse for mark to ligature where
          there can be many marks per anchor class (one per
          ligature position).</li>

          <li>Having done this make sure we don't use the same
          anchor point more than once.</li>

          <li>What glyph class should be used by default if a glyph
          is both a ligature and a mark? Probably mark. There are
          greek accent ligatures, and its probably more important
          to treat them as marks than as ligatures (I don't know
          any fonts which actually "skip ligatures" but there are
          lots which "skip marks").</li>

          <li>Select-&gt;Next/Prev Point always selected the first
          point. Select First point did the wrong thing.</li>

          <li>Pressing the [Refresh] button could crash ff if a
          "FontData" depended on another (same font).</li>

          <li>Someone (John ?Morrison?) requested a way to access
          fonts by numeric index rather than font name when opening
          font collections like ttc files or dfonts.</li>

          <li>* I no longer have separate l/lpotential and
          r/rpotential pairs Â&nbsp; of point data objects. Instead
          I use just 'l' and 'r' accompanied by Â&nbsp; boolean
          flags indicating their state as "potential". This greatly
          Â&nbsp; simplifies some tests and makes the code more
          readable. * When I am adding a chunk based on a single
          point to an existing stem, Â&nbsp; I always mark the
          second point as "potential". Later this state can Â&nbsp;
          be changed if check based on the second point produces
          the same chunk, Â&nbsp; or at least doesn't produce
          another (conflicting) stem. Again, this Â&nbsp;
          simplifies some tests which accompany adding new chunks
          and makes the Â&nbsp; result of the stem detection less
          dependent from the order in which Â&nbsp; the points are
          processed. * I allow assigning a point to a stem even
          when its distance from the Â&nbsp; stem edge is larger
          than standard dist_error_hv or dist_error_diag, Â&nbsp;
          if only the difference between maximum possible
          deviations to the Â&nbsp; both sides of the edge doesn't
          exceed the double dist_error_* value. Â&nbsp; This
          prevents us from adding several almost-coincident hints,
          actually Â&nbsp; controlling the same stem. * I have
          added a function which performs some stem normalization,
          Â&nbsp; sorting chunks by point coordinates. For HV stems
          it also can Â&nbsp; slightly modify the positioning of
          the stem edges preferring the Â&nbsp; coordinate which is
          closer to most points assigned to each edge. * There is
          now a special function used to compare conflicting stems
          Â&nbsp; and decide if one of these two should be
          preferred, or they both are Â&nbsp; worth to be output. *
          The detection of serifs and similar elements, which, not
          being Â&nbsp; exactly horizontal/vertical, still have to
          be marked with a HV Â&nbsp; stem, has been improved (two
          points, forming a serif termination, Â&nbsp; now should
          not necessarily follow each other).</li>

          <li>Drat. If we had libjpeg and not libpng we'd get a
          complaint about an undefined symbol.</li>

          <li>Add "Mismatch Unicode &amp; Name" to the Find
          Problems dlg.</li>

          <li>There are ttf files in existance where glyph names do
          not match unicode code points. Tons of fonts use
          ".notdef" for glyphs other than "GID=0". Other fonts use
          ASCII glyph names (space, exclam, numbersign,...) for
          glyphs in other scripts (Kedage-n.ttf does this).</li>

          <li>In the past, ff has felt that the presence of a
          zero-width ".null" and "nonmarkingreturn" glyph meant
          that a font was not mono-space. In the future ignore
          these glyphs when determining whether a font has fixed
          width.</li>

          <li>in some rare cases we got an uninitialized value in
          spline-&gt;line display conversion.</li>

          <li>Up the size of the File-&gt;Recent menu to 10, and
          include non-sfd files in the list.</li>

          <li>The routine to create an apple state machine from a
          set of OpenType ('init','medi','fina','isol') forms would
          often crash.</li>

          <li>When scaling BlueValues, or other arrays, a trailing
          space after the last number and before the ']' was
          considered an error. If found then ff would not scale
          that entry.</li>
        </ul>
      </li>

      <li>2-Oct-2007

        <ul>
          <li>Add
          <code>Edit-&gt;Select-&gt;Autohintable</code></li>

          <li>Typo in parsing cmap format=6 subtables could cause a
          crash (or eccentric behavior)</li>

          <li>Can build fontforge so that it is a python extension
          (as well as embedding python in ff).

            <blockquote>
              <pre>
$ ./configure --enable-pyextension
</pre>
            </blockquote>
          </li>

          <li>If a tt spline had a control point on top of an
          on-curve point we would lose track of it when generating
          the font.</li>

          <li>Add support for the Uncode variation subtable of the
          'cmap' encoding table (format=14).</li>

          <li>add xdg-open to the list of "known" browsers.</li>

          <li>Patch from Torsten Bronger. Got the args wrong in
          (python) font.glyphs.</li>

          <li>Fabrice Popineau &amp; Taco Hoekwater point out that
          in the featurefile output routines I was using a single
          backslash inside a printf string. The intent was to
          output a single backslash. But I actually need to quote
          the backslash with another to do that.</li>

          <li>If a text string were extremely long it could
          overflow the 16 bits allowed for a width in a metrixedit
          column. Truncate to 32767 in that case. Still can't
          scroll over the whole thing, but editing it will pop up a
          better view which will allow it all to be displayed.</li>

          <li>If there are no slots in the current encoding, then
          clicking on the encoding menu caused a crash.</li>

          <li>Give the user control over the code pages/unicode
          ranges fields of the OS/2 table. Add python scripting
          commands to access them too.</li>

          <li>When the user renames a glyph then things dependant
          on it should change too.<br />
            So if any substitution (or pairwise positioning) refers
            to the old name, change it to refer to the new.<br />
            If any contextual change refers to the old name change
            to the new.<br />
            If any class of glyphs (kerning class, apple state
            machine, contextual by classes) refers to the old name
            change to the new.

            <p>More debateable: if we change "f" to "u0066" then
            change "f.sc" to "u0066.sc" and "f_f_l" to
            "u0066_u0066_l" (and recurse on those name
            changes).</p>
          </li>

          <li>Guess at the meaning for GDEF glyph class component
          glyph:

            <ul>
              <li>Something not encoded</li>

              <li>Something which is refered to by at least one
              other glyph (as a reference)</li>

              <li>Something which is not generated by GSUB</li>
            </ul>
          </li>

          <li>Further improvements to the auto instructor.</li>

          <li>Make the [Guess] button in FontInfo-&gt;Private
          active when BlueScale is selected. (and make it work
          too).</li>

          <li>Oops. A font member in python was mis-named.
          Documented to be "loadState" was "loadStyle". Corrected
          to match the documentation.</li>

          <li>Some of the 'maxp' checks in the validator were off
          by 1, so fontlint would report errors on the glyph with
          the maximum value.</li>

          <li>Validator was checking non-composite glyphs against
          composite boundries.</li>

          <li>Barry Schwartz points out that I should validate the
          PostScript Private dictionary (Check that entries have
          the right types, check that BlueValues: has an even
          number of elements, is in order, that pairs are separated
          by bluefuzz*2+1, not too big for bluescale etc.).</li>

          <li>FF would crash when building accented glyphs from
          unicode data that included a space as the base
          glyph.</li>

          <li>Torsten Bronger points out that "import" is a python
          keyword and can't (easily) be used as a member/method
          name. So change the glyph.import function to
          importOutlines.</li>

          <li>Patch by Mathias Kilian OpenBSD needs an include file
          linux doesn't (or rather that linux imports in another
          include file) declaration statement mixup.</li>

          <li>Patch by Michal Nowakowski to disambiguate some
          strings and to make sure some others get translated.</li>
        </ul>
      </li>

      <li>17-Sept-2007

        <ul>
          <li>Patch from Daniel Johnson. FF didn't compile
          --with-regular-link</li>

          <li>And FF didn't compile if it had libpng but not
          libjpeg</li>

          <li>Added some warning messages when doing AutoInstr so
          that if a font does not contain a private dictionary, or
          if none of the selected glyphs contain hints, then let
          the user know s/he isn't going to get very useful
          instructions.</li>
        </ul>
      </li>

      <li>15-Sept-2007

        <ul>
          <li>Added the ability to upload a font to the <a href=
          "http://www.openfontlibrary.org/">open font library</a>.
          (You need to have created an account with them
          first).</li>

          <li>Further improvements to the auto instructor.</li>

          <li>When all glyphs are selected and the user
          auto-instructs, then FontForge will clear any legacy
          tables ('fpgm', 'prep' and 'cvt&nbsp;'). The old values
          will be of no use, and they just get in the way.</li>

          <li>Add a Edit-&gt;Select-&gt;Select by Script
          command<br />
          Make the Select by Name take a wildcard (so you could
          select "*.sc").</li>

          <li>ApplySubstitutions still had problems. Caused crashes
          in a font with instructions.</li>

          <li>If one used the metrics view to create a kerning
          lookup then: there would be no 'kern' feature in the
          feature list yet, and the display would randomly lose
          track of kern pairs and then create new ones. Very
          confusing.</li>

          <li>Hmm. In some cases Merge Fonts didn't copy over
          lookup info.<br />
          Add the ability to merge cross-font kerning pairs (in
          case the two fonts being merged have the same glyphs for
          those which are in both fonts).</li>

          <li>Provide a mass glyph rename menu item.</li>

          <li>The [Merge] button in Font Info-&gt;Lookups was
          disabled when two subtables in the first lookup were
          selected.</li>

          <li>If a glyph ended in a suffix (one.superior, etc.),
          then changes to that glyph were not reflected in the
          fontview.</li>

          <li>Add the ability to Populate a lookup from the
          selection (in the lookup sub-table dialogs)<br />
          Do a better job of providing default values for single
          substitutions &amp; positions.</li>

          <li>In the Print/Display dlg, deleting something so that
          the next line was blank caused ff to crash.</li>

          <li>The Encoding-&gt;Make From Font menu item should be
          disabled if the encoding is not custom.</li>

          <li>Fixed a system specific crash in the BDF Info
          window.</li>

          <li>Major rewrite of tilepath. Now has initial, medial,
          final &amp; isolated tiles which it will use depending on
          the circumstances. No longer uses the clipboard, but you
          can draw the tiles in the dlg.</li>

          <li>In Italic/Oblique fonts (those where the font has an
          italic angle specified) make the center in width command
          correct for the italic angle.</li>

          <li>Round to Int didn't round anchor points.</li>

          <li>The Control Point Info window could wander off the
          bottom of the screen. I was very carefully calculating
          its position -- and then not using the result.</li>

          <li>Inkscape stuffs bitmap images into svg files using
          the data URI<br />
            &nbsp; &nbsp;data:&lt;mimetype&gt;,&lt;data&gt;<br />
            (see IETF standard RFC 2397)

            <p>So, I'll support this now as my only way of handling
            type3 style svg fonts with embedded bitmaps.</p>

            <p>The standard points out that URIs are limited to
            1024 bytes, but I don't pay any attention to that
            restriction, and will stuff arbitrary sized images into
            these things.</p>
          </li>

          <li>The code that set up python import/export filters did
          not put an end of list entry after the last one.
          Sometimes it would be NULL (correct) and things would
          work and sometimes it would be garbage and things would
          crash.</li>

          <li>Drat. In the outline glyph view, the Import command
          didn't set the filter properly when you changed the
          import type.</li>

          <li>Extend fontforge to keep track of errors encountered
          when loading 'sfnt' files, and then have fontlint
          complain about them.

            <p>Also extend fontlint to do validity checking in
            glyphs against the 'maxp' table. (This won't matter
            when editing fonts, as ff will fixup the maxp values
            when it generates the font, but there might be some
            existing fonts with buggy 'maxp' values).</p>
          </li>

          <li>Oops. When changing the weight of a glyph and
          retaining the counter sizes, fontforge would push two
          entries onto the undo stack rather than one. (So the user
          would have to do Edit-&gt;Undo twice to get back to where
          s/he started from).</li>

          <li>Added several new python methods to font.

            <ul>
              <li>find(contour) will search the font for all glyphs
              containing contour and return an interator on that
              set.</li>

              <li>replaceAll(srch,rpl) Will search for the "srch"
              contour/layer in the font and replace it (each time
              it occurs) with the "rpl" contour/layer.</li>

              <li>glyphs(type) returns an iterator over all glyphs
              in the font. If present type may be "GID" (default if
              omitted) or "encoding" and it indicates the order in
              which the glyphs will be returned.</li>
            </ul>

            <p>Added some new members to glyph:</p>

            <ul>
              <li>encoding -- returns the glyph's encoding in the
              font</li>

              <li>script -- returns the OpenType tag (a 4 letter
              string) of the script of this glyph.</li>
            </ul>
          </li>
        </ul>
      </li>

      <li>31-August-2007

        <ul>
          <li>New traditional Chinese translation of the UI by
          Wei-Lun Chao.</li>

          <li>Updated Vietnamese translation by Clytie
          Siddall.</li>

          <li>Removed the old MetaFont command (which didn't work)
          and replaced it with a styles menu (incorporating the old
          Effects menu, and a command to change weight, to
          condense/extend, and to oblique. Added python scripting
          commands {font,glyph}.{changeWeight,condenseExtend}</li>

          <li>Lots of new work on the truetype autoinstructor by
          Alexej and Michal.</li>

          <li>Add a validation dialog which can be run just before
          generating a font.</li>

          <li>Try a different algorithm for approximating splines
          by line segments (for drawing them in the outline glyph
          view and elsewhere). This one should show symmetry
          better.</li>

          <li>Provide the ability to ask freetype to rasterize
          glyphs without hints in the Print/Display dlg (even if
          the glyphs have hints, rasterize them without).</li>

          <li>Oh dear, rasterizing stroked fonts only worked if
          multilayer was defined.</li>

          <li>Try to improve display of stroked fonts.</li>

          <li>When stroking splines don't let miter joins grow
          excessively.</li>

          <li>FF would remove instructions from glyphs that had at
          least two contours the first of which started with a
          control point.</li>

          <li>Add a short cut for Hide Grid in the metrics
          view.</li>

          <li>Python 2.5 initializes itself differently from Python
          2.[34]. 2.[34] delay the init until an import happens,
          while 2.5 does it at start up. I just assumed that when I
          called Py_Initialize that it did so. This led to a crash
          on 2.[34] when I tried to use my types before the user
          had tried to import fontforge.</li>

          <li>Further improvements to tile path.</li>

          <li>When moving a control point in a ttf font where one
          side of the cp was a real point, I would allow an
          implicit point on the far side of the real point to
          become real.</li>

          <li>When dragging truetype points around, adjacent
          implicit points would remain where they were (and not be
          implicit any longer).</li>

          <li>FF would randomly crash after removing a lot of
          glyphs.</li>

          <li>The knife tool would not cut a contour if it landed
          on a point.</li>

          <li>Trying to add a stylename to the size pane of
          fontinfo generally caused a crash.</li>

          <li>All blank lines in the display dlg had the same line
          spacing as that of the first character displayed in the
          dlg.</li>

          <li>I don't think feature files where handling classes
          defined with '-' properly.</li>

          <li>Read the "lib" structures from UFO/GLIF files into
          our python persistent data. (And write our persistent
          data out if it's a dict).</li>

          <li>Add the ability to call hooks (python functions) when
          various fontforge events take place.</li>

          <li>Make fontforge's basic types (Point, Contour, and
          Layer) be picklable so they can now be saved in an sfd
          file.</li>

          <li>Oops. With the inclusion of the library check
          argument, ff would not compile if NODYNAMIC were
          set.</li>

          <li>FontForge now stores the "userdata" python members
          into the sfd file as pickled objects. (FontForge's own
          types are not currently pickleable).</li>

          <li>Add the ability to mark a glyph so that just before
          being saved its references will be unlinked and we will
          run remove overlap on it. This means the user can work
          with the references (and get the automatic updating they
          confer) and still not have a self-intersecting glyph in
          the output (think Aring, Ccedilla, Eogonek).</li>

          <li>Create a fontlint script file.</li>

          <li>When dumping both apple and opentype bitmap tables if
          there were a BDF table, then we'd get garbage for
          'bloc'/'bhed'.</li>

          <li>Add some user interface commands to python, and more
          importantly, add the ability to create menu items which
          will invoke python scripts, and the ability to add
          import/export conversion filters (again, python
          scripts).</li>

          <li>Counter hints for LCG glyphs came out wrong if
          autohint had not been applied first.</li>

          <li>Counter masks were not read out of sfd files
          properly.</li>

          <li>Selecting a counter mask in Glyph Info caused FF to
          crash.</li>

          <li>The Execute Script dlg would sometimes complain about
          invalid scrollbar size when it got closed.</li>

          <li>AddAnchorPoint (scripting command) should be prepared
          to cast real args to integers.</li>

          <li>Just as I needed a special "in use" pass of GSUB when
          reading from a TTC, so I also need an "in use" pass of
          the MATH table.</li>

          <li>All this time and I've mapped "nonmarkingreturn"
          (GID=2) to Unicode+000C instead of Unicode+000D. I'm a
          twit.</li>
        </ul>
      </li>

      <li>08-August-2007

        <ul>
          <li>Support for MicroSoft's new 'MATH' opentype table.
          <a href="math.html">Element-&gt;Math Info</a>.</li>

          <li>Michal Nowakowski and Alexej Kryukov have improved
          truetype hinting.</li>

          <li>kerning display is off in a pairwise lookup window if
          a y position adjustment were requested.</li>

          <li>When reverting a compacted font ff thought the font
          was compacted even when it was not.</li>

          <li>Make some effort to retain context in the fontview
          when changing encodings.</li>

          <li>ff scripting command CopyReference() was broken.</li>

          <li>Werner wants little popup windows in show att. Give
          him some for substitutions.</li>

          <li>If you examined a kerning pair subtable (either with
          glyph info or from double clicking on the subtable in the
          lookup pane) and then pressed [OK], and then generated an
          afm (tfm, old-style kern table, etc.) you would lose all
          the kern pairs you examined.</li>

          <li>Patch by Barry SCHWARTZ to feature file output on
          64bit machines.</li>

          <li>In freetype 2.3.5 the binary layout of the execution
          context changed.<br />
            This means that if ff is compiled against a 2.3.4
            library it can't debug truetype if linked with a 2.3.5
            library (and vice versa).<br />
            So put in checks to see that the library version
            matches what we expect.

            <p>Also the contents of one of the structures has
            changed a bit, and a value that used to live in one
            field has moved to another (the ppem value moved from
            (exc)-&gt;size-&gt;metrics.x_ppem to
            (exc)-&gt;size-&gt;root.metrics.x_ppem.</p>

            <p>Well, David warned me that this might happen.</p>

            <p>Warn the user (rather than just silently failing)
            when we have a freetype version mismatch.</p>
          </li>

          <li>Patch from Barry SCHWARTZ. python
          fontforge.font.addPosSub was expecting its args inside a
          redundant tuple.</li>

          <li>New Vietnamese translation from Clytie.<br />
          Also some spelling corrections in the original
          messages.</li>

          <li>Patch by Barry SCHWARTZ to lookup/subtable
          comparison.</li>

          <li>If a metricsview was open, then creating a new glyph
          slot would potentially screw up memory and sometimes
          crashed.</li>

          <li>Edit-&gt;Merge (and simplify) still have bugs.</li>

          <li>Fix two memory leaks in the metrics view (one was
          huge).</li>

          <li>If freetype failed to rasterize a glyph, then we
          would fall back on returning a bitmap image from our own
          rasterizer -- even if we asked freetype for a greymap.
          this caused problems when routines expected byte data
          rather than bit data.</li>

          <li>If we were given a cff (otf) font, with a bluevalues
          array which ended in 0 (as [-20 0]) then we would omit
          the final zero ([-20]).</li>

          <li>Outputting extension subtables appears to have been
          broken.</li>

          <li>The code which was supposed to detect two glyphs with
          the same set of kerning pairs and use the same data for
          them didn't work (forcing us to get an extension table
          which also didn't work).</li>

          <li>Add some more checks against non-BMP characters when
          drawing text.</li>

          <li>For first characters in the kern pair dlg, when
          editing class 0, the [Edit] button was enabled but did
          nothing. Should work now.</li>

          <li>ff could crash if it tried to create a popup image of
          the &lt;New&gt; line in the substitution pane of Glyph
          Info.</li>

          <li>Horizontal Scrolling in the matrix edit widget
          sometimes forgot to move the column labels.</li>

          <li>Add glyph name completion to lookup subtable dlg and
          glyph info panes.</li>

          <li>addKerningClass didn't parse its arguments
          correctly.</li>

          <li>Drat. When printing full page glyphs to a pdf file,
          the glyph was shifted up by almost the full page and we
          got a second (and incorrect) title.</li>

          <li>MS proposes two new feature tags with it's new 'MATH'
          table.</li>
        </ul>
      </li>

      <li>23-July-2007

        <ul>
          <li>I have merged (and substantially rewritten) the Print
          and Display Dialogs. There is now only one menu item
          (Print) which (vaguely) the old Display dlg except that
          it can now be printed. The text area widget now supports
          OpenType features just as the metrics view does. It also
          supports ligature carets.

            <p>The dialog is no longer modal, however it does not
            get updated with each change to the font (that would
            make moving a point around in the outline view far too
            sluggish), instead there is a [Refresh] button the user
            can press to force an update.</p>
          </li>

          <li>It occurred to me that fontforge's current mechanism
          for setting ligature carets requires that there be a
          ligature substitution is the exact number of components
          used to make the glyph. But in indic fonts ligatures are
          often made up out of other ligatures (I think) which
          means that there won't be enough caret positions.

            <p>So I've added a Ligature Caret count to the
            Element-&gt;Glyph Info dialog to give the user control
            over it when necessary.</p>
          </li>

          <li>Add minimal support for applying apple state machine
          lookups in metrics view. Support is minimal because:

            <ul>
              <li>Apple seems to figure line breaks before doing
              substitution process but I do it afterward so I don't
              know where the line breaks are and I can't enter
              either the line start or line end state.</li>

              <li>When I delete a glyph I delete it. Apple inserts
              a deleted glyph mark and then removes that later.
              State machines can respond to deleted glyphs, but I
              can't.</li>

              <li>I don't try to figure out which feature,settings
              should be on by default. So the user must pick them
              out manually.</li>
            </ul>
          </li>

          <li>Add popup graphics to the Glyph Info and Lookup
          subtable dialogs to show substitutions (that is if there
          is an entry like 'smcp' a =&gt; a.sc then create a popup
          window showing the "a" glyph and the "a.sc" so the user
          can see what happens.</li>

          <li>Another futile attempt at an embolden command.
          Element-&gt;Embolden</li>

          <li>Add shortcuts to the anchor control dlg (Page Up/Page
          Down) to move to the next/previous glyph.</li>

          <li>Michal Nowakowski has improved the truetype
          autoinstructor. He warns that it probably still has bugs
          (as what does not?) so I am leaving the old code
          available for now. He says it works best in "a clean
          (uninstructed) font with well defined blue zones and
          stems".</li>

          <li>If we have a glyph with multiple encodings, and the
          secondary encodings occur after the primary ones, then
          the backmap will probably contain a secondary encoding,
          which means that when we go to load the font in we will
          probably notice the secondary encoding twice and forget
          the primary.</li>

          <li>I used not to distinguish between ligature anchors
          and normal mark to base anchors. Unfortunately when I
          moved to lookups (from features) I had to introduce that
          distinction. But I didn't work through all the
          implications and have fixed a number of bugs related to
          that.</li>

          <li>Barry SCHWARTZ complains that font info says
          "fontnames must" but that the cited adobe tech note only
          says "should". So change "must" to "should".</li>

          <li>When processing class-based contextual lookups
          fontforge could not handle class 0 (the class containing
          "all glyphs not in another class") add code to do
          that.</li>

          <li>If the user did not select a Gasp Version (note:
          active selection was needed, just seeing that it was
          correct and leaving it didn't work) then [OK] would leave
          the font with an invalid version and on some systems
          caused a crash.</li>

          <li>View-&gt;Insert Glyph After didn't work well on a
          ligature glyph. It would insert the glyph after the first
          component of the ligature, not after the last -- which
          would make more sense.</li>

          <li>Misnamed some private dict entries when loading from
          otf.</li>

          <li>Make entry of ghost hints better.</li>

          <li>Add the ability to determine whether a point is
          selected or not from python.</li>

          <li>Add a mechanism so the user can ask fontforge to
          check for the existance of optional libraries.</li>

          <li>Add range checks to some library routines which
          blindly referenced some BMP arrays with codepoints
          outside bmp. Broken by UCS2-&gt;UCS4 change.</li>

          <li>Werner wants GotoChar to be able to switch sub-fonts
          in a cid keyed font. This may introduce bugs...</li>

          <li>Revert glyph still wasn't working.</li>

          <li>Someone complained that using a negative stroke took
          a very long time but produced correct results. Um. Ok.
          It's easy always to use the absolute value.</li>

          <li>Oops. The mac uses UCS2 for filenames, so when I
          moved to UCS4 I should have changed the mac resource file
          interface.</li>

          <li>When creating a mac resource file we only set the
          type/creator fields and failed to initialize the
          finderFlags.</li>

          <li>Fixed crash bug in generating a cursive connection
          anchor sub-table.</li>

          <li>In TrueType composite glyphs with the USE_MY_METRICS
          bit set the lock icon wasn't scrolled properly.</li>

          <li>The change from UCS2 to UCS4 broke text
          copy/paste.<br />
          We failed to add a terminating NUL of the right size in
          all cases<br />
          We continued to use charset=UCS-2 when it should have
          been UCS-4</li>

          <li>FF crashed when trying to View-&gt;Show ATT on a font
          that appears to me to contain an invalid 'kern'
          sub-table. I have removed the proximate cause of the
          crash. I have provided a warning that the kern table
          appears invalid. And I have cleaned up my internals after
          detecting the bad sub-table (I had a lookup with a
          feature but no script and this caused problems).</li>

          <li>Multiple substitutions in the metrics view did not
          properly update the count of glyphs to be displayed.</li>

          <li>If nothing changed in the metrics input field and the
          output contained a ligature (or a mult subs I suspect).
          FF would complain.</li>

          <li>in python, font.generate() didn't work. The
          PyArg_ParseTupleAndKeywords behaves in a way I did not
          expect.</li>

          <li>[Bottom] and [Down] still didn't work for lookup
          subtables.</li>

          <li>Try to force the text field in the metricsview to a
          fixed size. In some fonts it seems to be initialized to a
          huge value.</li>

          <li>Add ability to display italic side bearings in the
          char view.</li>

          <li>The lines drawn for italic fonts to show the italic
          origin and width were at slightly the wrong angle (I used
          a sine when I should have used a tangent).</li>

          <li>If a font did not have any horizontal metrics then ff
          would not set the em-size.</li>

          <li>Show Att trampled on memory when displaying apple
          contextual substitution state machines.</li>

          <li>Wasn't parsing apple's 'lcar' table properly.</li>

          <li>if a font contained a 'post' table but didn't name
          all names (or something like that), then the attempt to
          name the glyph based on the encoding was broken after the
          encoding change.</li>

          <li>FF did not recognize that a bdf file was greymaped.
          Broken by the bdf properties work a year ago or so.</li>

          <li>The import lookups button in fontinfo forgot about
          the subtables (sort of).</li>

          <li>The metricsview used the wrong count field to
          determine whether things changed. It used the glyph
          count, not the char count (which meant that when we had a
          ligature and the number of chars was greater than the
          number of glyphs, things got confused.)</li>

          <li>In the metrics view, anchored attachments only worked
          if the base glyph were itself unmoved (that is the mark
          was placed relative to the unmoved location, not the
          actual location).</li>

          <li>The search dialog should provide user with control
          over the error bound.<br />
          The rotate checkbox didn't work if the flip checkbox
          wasn't checked.</li>

          <li>If a replace contour added a control point to a point
          that did not have one (went from a line to a curve) then
          that control point would get lost.<br />
          If a search matched across the start point of a contour
          then search/replace could go into an infinite loop if the
          search and replace paths were the same.</li>

          <li>Find/Replace (replace) didn't work on quadratic
          splines.</li>

          <li>Add two python methods:

            <ul>
              <li>
              Layer.interpolateNewLayer(other-layer,amount)</li>

              <li>
              Font.createInterpolatedGlyph(glyph1,glyph2,amount)</li>
            </ul>

            <p>The first creates a new layer by interpolating
            between the current layer and the layer in the first
            argument.<br />
            The second creates a new glyph in the font by
            interpolating between the first two arguments. The
            glyph's unicodecode point and name will be copied from
            the first argument (the font must not already contain
            this glyph).<br />
            If amount is 0 the result will look like the first
            glyph, if 1 then like the second.</p>
          </li>

          <li>When recovering from a crash, FF would sometimes
          complain about a mismatched version number. Don't.</li>

          <li>Problems parsing 'mort' tables could cause a
          crash.</li>

          <li>When building a contextual lookup, don't list that
          lookup as something that it could invoke (ie. list all
          lookups in this table (GPOS/GSUB) except for ourselves).
          Don't want to encourage users to create infinite lookup
          loops.</li>

          <li>Point matching didn't work when there were references
          to references and multiple references within a
          glyph.</li>

          <li>FF was having problems with extension lookups with
          multiple sub tables.</li>

          <li>We were trying to print a trailing NUL in some
          strings from the fontview.</li>

          <li>Kerning by classes got broken in metricsview by the
          addition of support for device tables.</li>

          <li>A GPOS contextual lookup only listed GSUB lookups in
          the lookup/sequence dlg<br />
          Pressing [OK] in the lookup/sequence dlg caused a crash
          if no lookup selected.</li>

          <li>Openfontdlg was looking at the filter listbutton
          rather than the rename namelist listbutton.</li>

          <li>mf2pt1 now uses "glyph_dimensions" rather than
          "bbox"</li>

          <li>The metrics view should now handle device
          tables.</li>

          <li>Goto could crash when used on small encodings.</li>

          <li>-lang wasn't permitted before -c.</li>

          <li>Use numeric text fields for anchor positioning.</li>

          <li>Graham Asher points out that the meanings of
          underline position in the 'post' table and the FontInfo
          dictionary are different. One refers to the top of the
          underline rectangle and one to the center of it.</li>

          <li>Align point would crash if the selected point were
          the end point of a contour (or if the two points around
          it were in the same place).</li>

          <li>The baseline was not properly located when displaying
          it in the fontview.</li>

          <li>The scripting command BitmapsAvail would generally
          cause FF to crash if done when there was a UI..</li>

          <li>We seem to be misimplementing my obsolete (sfd file)
          convention for having duplicate encodings point to the
          same glyph. Result was that occasionally a glyph would be
          removed and a pointer to something it refered to would be
          put in its place.</li>

          <li>Change the name of activeFontInUI to activeFont<br />
          Add an activeGlyph method.<br />
          Add the ability to call a python script from a outline
          view.</li>

          <li>Hmmm. If a textfield is shifted right, and then
          resized so there's now room for all the text, the unshift
          it.</li>

          <li>Werner suggests that it would be useful to be able to
          specify wildcards in the goto dlg.</li>

          <li>Michael Zedler tells me that glyphs output by mf2pt1
          contain a line:
            <pre>
 % MF2PT1: bbox 0 90 834 422
</pre>

            <p>where the third (so called) bounding box entry is
            actually the glyph's advance width. I was reluctant to
            use this at first, because that clearly isn't something
            that belongs in a bounding box...</p>
          </li>

          <li>Werner tells me that lilypond uses a slightly
          different syntax for the MF2PT1 bbox comment, so make our
          parsing slightly more generous.</li>

          <li>When creating a new lookup subtable for an anchored
          lookup, it did not get marked as having anchor classes
          and feature file output failed because of that.</li>

          <li>When outputing single lookups, the feature, script
          and language tags all had ^A where they should have had
          the second letter of the tag.</li>

          <li>Remove the code to produce the old, broken, 'size'
          feature.</li>
        </ul>
      </li>

      <li>07-June-2007

        <ul>
          <li>Add support for Adobe's feature file syntax.<br />
            Use Merge Kern (now Merge Feature) to read one<br />
            Use Element-&gt;Font Info-&gt;Lookups-&gt;popup
            menu-&gt;Save to generate one

            <p>Sigh. Adobe documents a feature file syntax they
            don't fully support, and even their documented syntax
            is inadequate to represent all the complexities of
            OpenType.</p>

            <p>FontForge supports anchors and device tables and
            will parse lookups which contain these. This is a
            syntax which Adobe documents but does not implement.
            Adobe also warns that this syntax may change when they
            get around to implementing it.</p>

            <p>FontForge makes one extension to the syntax which
            allows me to specify complex contextual features.</p>

            <p>Neither I nor Adobe support reverse contextual
            substitutions, nor GDEF mark classes.</p>
          </li>

          <li>Add a popup menu to the lookups pane of font
          info.</li>

          <li>Change the name of <code>File-&gt;Merge Kern
          Info</code> to <code>File-&gt;Merge Feature
          Info</code></li>

          <li>Remove the code to produce the old, broken, 'size'
          feature.</li>

          <li>An earlier patch, designed to make the tabset work in
          the charview even if the user changed the name, didn't
          work.</li>

          <li>Bug in the selection iterator.<br />
          Also Max Rabkin points out the docs say the iterator
          returns selected glyphs rather than encoding slots. Fix
          the docs, then add a member (.byGlyphs) which will make
          the iterator return glyphs.</li>

          <li>Accept contour += (1,2) rather than forcing people to
          say contour += fontforge.point(1,2)</li>

          <li>Was using an error return from two setter functions
          (contour.set_closed, set_is_quadratic) when I should have
          returned success.</li>

          <li>Crash when mistyping a glyph name in Glyph Info
          possub panes. Probably in the equivalent lookup dlgs
          too.</li>

          <li>If a glyph contained two copies of another glyph, and
          one of those copies was off by enough that ff didn't
          recognize it, the depending on how the contours were
          ordered, ff might fail to recognize the first glyph too,
          even though it did match.</li>

          <li>Add iterators to contours and layers. Python users
          seem to expect them even when they aren't documented to
          exist.</li>

          <li>layer += contour didn't work in python. I was
          examining a bit through the wrong data type.</li>

          <li>Provide a mechanism for copying lookup information
          from one glyph to another. (<code>Edit-&gt;Copy Lookup
          Data</code>)</li>

          <li>Loading kerning info from a mac 'FOND' resource was
          broken by the lookup change.</li>

          <li>Python scripting command font.createChar didn't.
          Partial patch from Max Rabkin.</li>

          <li>Adding a kerning pair from the metrics view would
          often add two or three pairs with the same character
          combination and different values.</li>

          <li>Another remove overlap bug. Introduced recently.</li>

          <li>Reinstate Apply Substitutions scripting command.</li>

          <li>Add some dutch styles.</li>

          <li>Make yet another attempt to correct for rounding
          errors when loading a postscript font.</li>

          <li>Add a way to get a font's filename to python.</li>

          <li>Werner points out that in scripting I use "break" in
          an example. It isn't documented to work and I don't
          implement it but I do show it. Oops. Ok, make it
          work.</li>

          <li>Display substitutions was broken.</li>

          <li>When generating default names for subtables, it is
          confusing to name them the same as the lookup.</li>

          <li>Change to using USC4 from UCS2 internally.</li>

          <li>Provide default names for lookups once the user sets
          the feature.</li>

          <li>Disambiguate some strings for the polish
          translation</li>

          <li>Revert glyph should not work for old sfd files.</li>
        </ul>
      </li>

      <li>11-May-2007

        <ul>
          <li>Loading some afm files would go into an infinite
          loop. (Introduced 9-May)</li>

          <li>[Import] button on Font Info-&gt;Lookups
          crashed.</li>

          <li>Fix a number of problems related to anchor
          classes.</li>

          <li>After the user does an [Add Lookup] we should select
          the new lookup, to make it easier for him/her to do an
          [Add Subtable].</li>
        </ul>
      </li>

      <li>9-May-2007

        <ul>
          <li>When ff parsed an afm file it only read the first
          ligature on a line.</li>

          <li>The [Call...] button in the scripting dialog is
          meaningless for python scripts (or I don't know how to
          give it meaning) so disable it.</li>

          <li>Vertical scrolling in the metrics view tried to
          scroll the list of features too.</li>

          <li>Tab, and arrow keys didn't work in the matrixedit
          widget after I added hidden columns. Make Return do the
          expected thing (move to start of next line and create it
          if possible).</li>

          <li>Patch by Pierre to fix uninitialized value when
          compacting encodings.</li>

          <li>Typo in realloc of lookups meant that nothing
          happened (when it should have increased array size by
          1).</li>

          <li>Add the OFL icon to the fontinfo dlg.</li>

          <li>Plugins were broken with regular link configure
          option.</li>

          <li>Inkscape can start X on the mac before it tries to
          connect. Hmm. I can do that too. Inkscape manages to
          start X without an xterm. I don't know how to do
          that.</li>

          <li>When reading PS and CharStrings, the closepath
          operator didn't allow for rounding errors.</li>

          <li>Metrics View would crash if more than 20 glyphs
          entered.</li>

          <li>Alexej Kryukov points out that it would be nice if
          moving an anchor point did not set "changed since last
          hinted.</li>

          <li>Alexej Kryukov points out that the "changed since
          last hinted" flag gets set inappropriately.</li>

          <li>Alexej Kryukov points out that the Anchor control
          menu item looked as though it had changed, but actually
          had not.</li>
        </ul>
      </li>

      <li>1-May-2007

        <ul>
          <li>I've redone the way FontForge handles lookups so that
          it is more in keeping with OpenType.

            <blockquote>
              The major change is that fontforge now presents
              lookups to the user rather than features. I think
              this makes simple things more difficult (which is why
              I avoided this when I started), but it makes complex
              things possible.

              <p>Sadly the world is not simple.</p>

              <p>So when a piece of typographic information is
              created (a ligature, a kern pair, a glyph
              substitution, etc.) it must be tagged with a lookup
              (actually a lookup sub-table) rather than a feature
              tag.</p>

              <p>The lookup itself will be tagged with a feature
              tag (possibly several tags) and with scripts and
              languages in which that lookup should be
              active.<br />
              <strong>NOTE:</strong> This reverses the way
              GPOS/GSUB think about things, but it contains the
              same information.</p>

              <p>The <a href="fontinfo.html#Lookups">Font Info</a>
              dialog now contains a Lookup pane which allows you to
              create and edit lookups and their subtables. You can
              also reorder them. The order shown in the dialog is
              the order in which they will be applied.</p>

              <p>A mac feature/setting subtable also gets converted
              into this format.</p>

              <p>The Font Info dialog no longer has Anchor Classes,
              Contextual, or State Machine panes.</p>

              <p>Instead you can edit a lookup subtable's data (for
              any subtable type). There are new dialogs which list
              all the information for each lookup type (ie. a
              dialog which lists all kern pairs in a subtable), and
              these provide access to the old anchor class,
              contextual or state machine dialogs.</p>

              <p>The Glyph Info command has also changed. It looks
              simpler and more comprehensible (I think), but the
              act of creating a new substitution has become more
              complex because (potentially) one must create a new
              lookup and lookup subtable before doing the simple
              task of adding a new replacement glyph.</p>

              <p>The kerning class, contextual and state machine
              dialogs have all changed in that they no longer
              request a feature tag, they now need a lookup
              subtable.</p>

              <p>The metrics view also needs a subtable.<br />
              The metrics view has changed considerably.<br />
              It displays all the features in the font, and allows
              you to select which ones you want active in the view.
              It lets you set the script &amp; language. It will
              apply lookups that it couldn't handle previously like
              ligatures and contextuals.</p>

              <p>It does not do Indic glyph reordering. I'm not
              sure how to and last I checked MS had not updated
              their docs to reflect their new procedures.</p>

              <p>Many other dialogs now take a lookup subtable
              where appropriate.</p>

              <p>Show ATT has changed, but it is still not
              editable. I hope that the Lookups pane will do that
              instead.</p>

              <p>There used to be a scripting command which
              indicated what ligature features got stored in afm
              files. Now each ligature lookup has a flag set on it
              which conveys this information.</p>

              <p>The Element-&gt;Typographic Features menu has been
              removed. It's functionality has moved into Font
              Info-&gt;Lookups (I hope I've got everything).</p>

              <p>Some scripting commands have been removed, others
              have been changed and others have been added. I
              apologize for this, as it will break existing
              scripts, but some basic concepts no longer exist and
              others, very different, have replaced them. (and
              anyway people may switch to <a href=
              "python.html">python scripting</a> now).</p>

              <dl>
                <dt>Removed:</dt>

                <dd>
                  <pre>
         DefaultATT
         ControlAfmLigatureOutput
         ApplySubstitutions
         CopyGlyphFeatures
         AddATT         Replaced with AddPosSub
         RemoveATT
         GlyphInfo(Position/Pair/Substitution/AltSubs/MultSubs/Ligature)
         SelectByATT    Replaced with SelectByPosSub
         
</pre>
                </dd>

                <dt>Changed</dt>

                <dd>
                  <pre>
         Set(V)Kern takes an optional third argument, a lookup subtable
              name (if not specified it choses one)
         AddAnchorClass(name,type,lookup-subtable-name)
         GetPosSub(subtable-name)
         AutoKern(spacing,threshold,subtable-name[,kernfile])
         
</pre>
                </dd>

                <dt>Added</dt>

                <dd>
                  <pre>
        AddLookup(name,type,flags,feature-script-lang-array[,after-lookup-name])
             n*[feature-tag,script-lang-array]
             n*[script-tag,lang-array]
             n*[lang]
         GetLookupInfo(lookup-name) =&gt;
        [type,flags,feature-script-lang-array]
         AddLookupSubtable(lookup-name,subtable-name[,after-subtable-name])
         GetLookupOfSubtable(subtable-name)
         GetSubtableOfAnchorClass(anchor-class-name)
         AddPosSub(subtable-name,variant(s))
                  (subtable-name,dx,dy,dadv_x,dadv_y)
                  (subtable-name,other-glyph-name,dx,dy...)
         RemoveLookupSubtable(subtable-name)
         RemoveLookup(lookup-name)
         MergeLookupSubtables(subtable-name1,subtable-name2)
         MergeLookups(lookup-name1,lookup-name2)
         SelectByPosSub(subtable-name,search_type)
         GetLookups("GPOS"/"GSUB")
         GetLookupSubtables(lookup-name)
         LookupStoreLigatureInAfm(lookup-name,store-it)
         LookupSetFeatureList(lookup-name,feature-script-lang-array)
</pre>
                </dd>
              </dl>

              <p>The <a href="sfdformat.html">sfd format</a> has
              changed. New files are tagged as version 2. Old files
              will still work, but ff will no longer produce file
              in the old format.</p>
            </blockquote>
          </li>

          <li>New translations to match the new UI: Polish, Greek,
          German, French, simplified Chinese.</li>

          <li>FontForge now supports <a href="python.html">python
          scripting</a> if it has been configured to do so.</li>

          <li>Tell users they should add their email address to the
          License after pressing the [Add SIL Open Font License]
          button.</li>

          <li>The metrics view had numerous problems. Most
          significant if a glyph changed elsewhere the metrics view
          would not be updated.</li>

          <li>If the width of a glyph changed in the metrics view
          then that was not synchronized to dependent glyphs.</li>

          <li>Enforce the "Use My Metrics" bit of a
          reference.<br />
          In TrueType, if this bit is set on a reference then then
          width of the containing glyph will be the same as that of
          the reference.<br />
          So don't let the user change the width of such glyphs.
          (and add a lock icon to the width line in the character
          view to show that it is fixed).</li>

          <li>Fix a number of Remove Overlap bugs.</li>

          <li>FF would destroy memory in the metrics view if the
          user attempted to display a character which was not in
          the font.</li>

          <li>Was setting the last char index (of OS/2) incorrectly
          if the font contained non-BMP characters. Might also have
          set the first char index wrong two.</li>

          <li>Bugs in 'PfEd' table, glyph comment subtable.</li>

          <li>Couple of places where I actually say "FontForge
          1.0". Let's bump that to 2.0 now that I've done that for
          the sfd format.</li>

          <li>Overlap problems with incorrect path
          orientations.</li>

          <li>Arrow keys didn't work in the charview if the tabset
          were active.</li>

          <li>I used to use "&gt;&lt;" on the font's window title
          to represent a compacted font. No one understood it. Use
          "Compacted" instead.</li>

          <li>Philipp Poll wants to see the side bearings (I think)
          in the charview.</li>

          <li>Nicolas Spalinger of SIL suggests a help button next
          to [Add OFL] to open a browser on the official OFL
          site.</li>

          <li>Patch from Nicolas Spalinger of SIL regarding the
          verbiage surrounding the OFL in the fontinfo. Also his
          suggestion to make the tooltip live longer.</li>

          <li>Replace with Reference didn't check reference offsets
          correctly.</li>

          <li>Find problems didn't find references which
          intersected.</li>

          <li>Add some standard classes to the context chaining
          dlg.</li>

          <li>Make sure we only generate a postscript name in the
          name table once.</li>

          <li>The change length button of the cvt dlg didn't
          work.</li>

          <li>Input/Output of Apple's 'lcar' table was
          inconsistent. I don't know if it is "right" now, but at
          least ff can read back what it wrote.</li>

          <li>Werner points out that the debug windows show up at
          odd places if the window gets resized.</li>
        </ul>
      </li>

      <li>12-Mar-2007

        <ul>
          <li>Add a button to insert the <a href=
          "http://scripts.sil.org/ofl/">SIL Open Font License</a>
          into the 'name' table.</li>

          <li>FF failed to store TeX heights and depths properly in
          a tfm file. FF failed to read or write TeX extension
          lists properly.</li>

          <li>Patch from Reuben Thomas to turn off the splash
          screen from the preference dlg.</li>

          <li>I had the dotlessj code point wrong. Again.</li>

          <li>FF did not center the charview window well on an
          empty glyph.</li>

          <li>The scripting command to add instructions to a glyph
          could immediately lose them if the glyph's points weren't
          numbered properly</li>

          <li>We used to allow the syntax
          "&lt;number&gt;&lt;numbers&gt;* command" in ttf
          instructions (which automagically inserted an implied
          push). Someone noticed that

            <blockquote>
              <pre>
PUSHB_1
1
2
</pre>
            </blockquote>

            <p>would lose the second number and not complain. In
            fixing that, I broke the first. Now both should work (I
            hope).</p>
          </li>

          <li>Code which I hope will handle German keyboards and
          make them do what the menu says they (ignoring the shift
          key) should for certain hot keys (brackets, curly
          brackets, brokets all get different modifier sequences on
          a german keyboard than an english).</li>

          <li>If a glyph had no hints then ff could add a hintmask
          operator (which didn't try to control any hints). Now I
          can't find anything in the docs which SAYS it's illegal
          to have a hintmask in a glyph with no fonts, it does seem
          bad practice, and a program called tx.exe complained
          about it.</li>

          <li>Patch by Michal Nowakowski to allow a nicer notation
          for delta instructions in the instruction editing window:
          Example:<br />
          <tt>PUSHB_3 6@12 8 1 DELTAP2</tt><br />
          This moves point 8 by six delta-steps (that's clear) at
          37 ppem (that's not clear at first glance - assuming
          delta_base is 9, DELTAP2 works from 25 ppem to 25+15
          ppem, in this example it's 25+12 ppem). So it's just a
          way of constructing an argument byte for DELTAP/C.</li>

          <li>Allow FontForge's menu shortcuts (hot keys, whatever)
          to be user definable. We use a gettext based mechanism,
          type $ make FontForge-MenuShortCuts.pot to get a pot file
          for the process. It needs to be converted to an mo file
          and installed in
          $(prefix)/share/locale/$(LANG)/LC_MESSAGES, just like any
          other getext file.</li>

          <li>The Export scripting command did not work as
          documented. It is documented to export all
          <em>selected</em> glyphs. Instead it exported
          <em>all</em> glyphs.</li>

          <li>Redo the anchor control dlg.</li>

          <li>Be a little more lenient about bitmap bounding boxes
          for empty glyphs when loading bdf fonts</li>

          <li>Make the ClearHints scripting command take arguments:
          "Horizontal" or "Vertical" to allow users to choose to
          clear either horizontal or vertical hints (the old form
          with no args still works and clears both, of
          course).</li>

          <li>Typo gives us an unititialized variable when saving
          ufo.</li>

          <li>Various problems to various anchor dialogs.</li>

          <li>If an anchor point contained an x devtab but not a y
          devtab then it produced a pointer to garbage for the y
          devtab instead of NUL.

            <p>Pairwise positioning lookups could also get their
            device table offsets screwed up.</p>
          </li>

          <li>Werner points out that if you have a series of the
          same glyph in a row in the encoding (generally .notdef)
          and you are in a char view, then pressing Next Glyph does
          nothing. You are stuck at the same code point. (same
          thing happens for Prev Glyph).</li>

          <li>a chinese input method steals keystrokes I use for
          hot keys (I think). So if users don't want glyph
          navigation by typing characters in the charview
          (controled by a preference item) then don't turn on the
          input method when the window is created.</li>

          <li>Add hot key for Select-&gt;Points on selected
          contours.</li>

          <li>Assign "dotlessj" to map to 0x237, the unicode code
          point, rather than to 0xf6be, the old Adobe private use
          area. !!!! THIS DOES NOT CONFORM TO THE AGL !!!!!</li>

          <li>Oops. The gloss for the shift point/contour/zone was
          slightly off and gave the wrong information.</li>

          <li>Add vietnamese font styles (bold, italic, regular,
          etc.)<br />
          From Clytie Siddall.</li>

          <li>Fixes for rounding errors in finding spline
          intersections.</li>

          <li>Werner points out that removing a bitmap glyph from
          the bitmapview does not force a redisplay in the
          fontview.</li>

          <li>Gleep. Werner points out that when generating bitmap
          strikes, ff would always generate a temporary postscript
          font to rasterize, so any truetype instructions would be
          ignored. And the generated strikes would be ugly.</li>

          <li>Add a command to show anchor point attachments within
          the outline character view<br />
          (View-&gt;Combinations-&gt;Anchor Glyph at Point)</li>

          <li>Force point numbers to be correct when changing
          glyphs in the charview.</li>

          <li>Add support for Apple/Adobe's obsolete 'typ1' sfnt. A
          way of stuffing a type1 font into an sfnt wrapper.</li>

          <li>Even though the viewbox/output width height ratios
          are different, people want the image scaled the same in
          svg input.</li>

          <li>People would like to have only one charview and
          double clicking in the fontview just changes the contents
          of an existing window.<br />
          Preference Item: OpenCharsInNewWindow</li>

          <li>Add a tabs line to the outline char window. If users
          are going to have only one charview open then they
          probably want some history too.</li>

          <li>Werner points out that what I call "Type42 CID"
          should actually be called either "Type11" or "CID Type
          2".</li>
        </ul>
      </li>

      <li>20-Dec-2006

        <ul>
          <li>Patch by Johan Winge fixing a bug in dragging out a
          magnification rectangle</li>

          <li>Patch from SUSE fixing a variable which can be
          uninitialized.</li>
        </ul>
      </li>

      <li>19-Dec-2006

        <ul>
          <li>I have received many complaints about the grey
          background, so I have tried various other backgrounds --
          and gotten complaints on all of them. Currently try using
          a white background by default and add a <a href=
          "faq.html#background">discussion in the FAQ</a> about
          changing it.</li>

          <li>Add support for Unified Font Objects (a directory
          holding many Glyph Interchange Format files). People at
          the Open Font Library seem to think this is useful. Also
          support for importing/exporting glyphs in glif.</li>

          <li>People asked me to implement the UFO/GLIF format in
          part because each glyph is stored in a separate file
          giving finer granularity to version control. I worry
          about using UFO/GLIF because it is not documented to
          store all the information needed to regenerate a font
          (being mainly concerned with glyph outlines). So I've
          implemented a directory based version of the sfd format
          which I hope will provide the one glyph per file format
          people say they want.</li>

          <li>MS has extended the 'gasp' table to give users
          control over clear type. Version number has changed too.
          FF now supports the new bits.</li>

          <li>MS has also added a cleartype bit to the head
          table.</li>

          <li>Hmm. I wasn't setting the apple specific bits of the
          head table properly.</li>

          <li>Allow the user to create an empty bitmap strike.</li>

          <li>Add the ability to remove bitmap glyphs from a
          strike.</li>

          <li>Fix a couple of memory leaks.</li>

          <li>The docs don't mention this, but... mangal.ttf has a
          NULL offset for the lookahead class definition, so if
          that happens -- no classes.</li>

          <li>Werner doesn't like that I always add dummy bitmaps
          for .notdef, .null &amp; nonmarkingreturn. It seemed
          logical to me that if I were prepared to add those glyphs
          to the outline font I should be prepared to add them to
          the bitmap strike. But Werner (I think) sees bitmap
          strikes as containing exceptional glyphs which need
          special handling, whereas I just saw them as complete
          fonts. So in this context I guess there is no need to add
          these glyphs. As a compromise I have decided that I will
          add the glyphs to the bitmap strike if I added the glyphs
          to the outline font.</li>

          <li>Add scripting functions:

            <ul>
              <li>SelectMoreIf</li>

              <li>SelectMoreSingletonsIf</li>

              <li>SelectSingletonsIf</li>
            </ul>
          </li>

          <li>The changed flag wasn't being set in Remove ATT.</li>

          <li>GetPosSub scripting command trashed memory.</li>

          <li>Make default char of OS/2 be space for otf and
          .notdef for ttf. This is a guess at what should be
          done.</li>

          <li>FF was still setting firstcharindex in OS/2
          incorrectly. The problem is that glyph 1 (or 2?) has
          encoding 0 in the mac cmap table while it is not
          referenced at all in the windows cmap.</li>

          <li>Wasn't setting os2_typelinegap field when reading an
          sfnt.</li>

          <li>In a font without any LCG characters, fontforge set
          the OS/2 capheight and xheight fields to -1e10. It should
          have been 0. Patch by Roozbeh Pournader.</li>

          <li>Patch by Roozbeh Pournader. Regular bit in fsSel in
          OS/2 was being set when it should not have been.</li>

          <li>Werner suggests that when looking at a bitmap strike,
          nextdef and prevdef look at the next glyph defined in the
          strike rather than the font as a whole. Useful for sparse
          bitmaps</li>

          <li>Werner wants to be able to set bitmap magnification
          in the font view.</li>

          <li>The "Recalculate Bitmaps" button in the bitmap view
          should adjust its positioning as the window is resized
          (and be sensitive to other languages which might have
          different button widths).</li>

          <li>there was an uninitialized variable used in parsing
          contextual by coverage table.</li>

          <li>Werner points out that when double clicking on a
          bitmap glyph in the font view, the glyph is created /
          rasterized without using freetype.</li>

          <li>Sigh. Ok. make the size of the label font in the
          fontview configurable.
            <pre>
fontforge.FontView.FontSize: 24
</pre>
          </li>

          <li>Werner finds "Original" confusing for an encoding and
          suggests "Glyph Order" instead.</li>

          <li>MS has revealed the meaning of a few new GETINFO
          bits. Put them in the Gloss window.</li>

          <li>Set/Select aren't very informative in class
          definition windows, change to "Set from font"/"Select in
          Font"</li>

          <li>Improve the way glyphs are centered in the outline
          char view. At least I hope it's an improvement.</li>

          <li>Oh. It is perfectly legal to have a context chain
          rule with no substitutions. This can be used to avoid
          matches in complex cases so:
            <pre>
[a-z] a b =&gt; does nothing
a b [a-z] =&gt; does nothing
a b =&gt; substitutes
</pre>

            <p>will only substitute of "ab" is a word all to
            itself.</p>
          </li>

          <li>If the metrics view were displaying text containing
          non UNICODE characters then some edits in the text field
          which displays glyphs would leave us with the replacement
          character showing instead.</li>

          <li>Werner wants to know whether storage locations are
          uninitialized or not, and to get warnings when reading an
          uninit value.</li>

          <li>Werner wants to see IF statements indented in
          truetype instruction display.</li>

          <li>FF wasn't telling freetype to set the mono bit when
          loading a glyph, which meant that GETINFO would return
          the wrong value for mono rasterization.</li>

          <li>If there are too many numbers after an NPUSH[BW]
          instruction, FF silently ignores them.</li>

          <li>Anti-Aliased rasters still weren't aligned properly
          with the outlines in the debug window.</li>

          <li>When debugging I provided popup information for
          anti-aliased rasters. But I didn't for mono rasters.</li>

          <li>ff would crash when asked to debug fpgm/prep (because
          my rasterization routine didn't work if there were no
          contours).</li>

          <li>Werner wants to turn off auto goto in the charview
          when debugging is going on.</li>

          <li>The gloss information for delta point (and cvt) was
          wrong if the magnitude selector was 7. I claimed it moved
          (changed) by 0, when it should have been by -1.</li>

          <li>Werner wants to be able to set memory watch points on
          storage and cvt locations. Set these through the
          cvt/storage windows by clicking on the appropriate
          locations. Modify the points window so the user can set
          watch points by clicking on it too.</li>

          <li>The Points window would sometimes scroll in
          unexpected ways.</li>

          <li>Werner wants to see the raw value of a "WS"
          instruction in the gloss.</li>

          <li>merge fonts would get the script lang index of merged
          kern pairs wrong.</li>

          <li>Correct some of icc's warnings</li>

          <li>Apostolos points out that NAME_MAX isn't defined on
          solaris, but _POSIX_NAME_MAX is. But _POSIX_NAME_MAX
          doesn't seem to be defined on linux.</li>

          <li>Display fonts would crash if you tried to change the
          font. But introduced in last release.</li>

          <li>Patch from Mike FABIAN. Rasterizing by freetype only
          initialized a variable if CONFIG_TYPE3 (multilayer) was
          set.</li>

          <li>StrSplit &amp; StrJoin scripting functions.</li>

          <li>Patch by RÃ¼diger Oertel. Strncat could overflow a
          buffer.</li>

          <li>Make simplify do point categorization, and not just
          of points changed.</li>

          <li>Curved stems are also limited by geometry. Can't just
          assume control points work.</li>

          <li>Why are pdf files listed as a source of bitmap
          fonts?</li>

          <li>When examining a bitmap font, metrics view would
          crash when asked to look at a non-existant glyph.</li>

          <li>The list of verbs for indic glyph rearrangement
          didn't display.</li>

          <li>Converting from the mac korean encoding didn't
          work.</li>

          <li>Images imported into a bdf character did not set the
          character used bit.</li>

          <li>Add a CopyAnchors command.</li>

          <li>Patch from Raph Levien. FF mishandled seac if the
          accent were not translated.</li>
        </ul>
      </li>

      <li>26-Oct-2006

        <ul>
          <li>If a large group of glyphs were autohinted at once,
          and one of those glyphs contained a reference to a glyph
          that appeared after it in the font, then that glyph would
          still end up with the dirty hint mark set.</li>

          <li>It was impossible to set preferences on the Accents
          pane. They would either always be 0 (or false), or make
          spurious complaints.</li>

          <li>Add a Ucs4 scripting command (reverses Utf8).</li>

          <li>when creating an array with [...] notation (in
          scripting) I forgot to dereference lvalues.</li>

          <li>Add scripting commands

            <ul>
              <li>Revert</li>

              <li>RevertToBackup</li>
            </ul>

            <p>Make the "+" operator concatenate arrays</p>
            <pre>
  [1,2] + [3,4] == [1,2,3,4]
  [1,2] + 3 == [1,2,3]
</pre>
          </li>

          <li>Add a scripting command, FontImage, which generates a
          font thumbnail.</li>

          <li>Make it possible to save the Font Display dlg as an
          image.</li>

          <li>Clean up the Display dialog a bit. The concept of
          "unhinted" truetype is obsolete. Remove it.</li>

          <li>At Andrey V. Panov's request I have added a scripting
          command "CopyUnlinked" which behaves like Copy except
          that any references will be unlinked (turned into
          splines) as they are placed in the clipboard.</li>

          <li>I believe OpenType would prefer if formed arabic
          glyphs didn't use their unicode encodings, but used
          simple substitutions instead. Accept both for svg output
          (previously we only accepted unicode encodings).</li>

          <li>Patch from debian (bug392688) from Wojciech Mu*a and
          K*stutis Bili*nas</li>
        </ul>
      </li>

      <li>19-Oct-2006

        <ul>
          <li>Patch from Mike FABIAN, array overflow in creating PS
          Private dialog</li>

          <li>The instructions out of date flag was only getting
          reset if the user made a change in the edit instrs
          dialog. If s/he just pressed [OK] it would remain
          on.</li>

          <li>Make libintl be another library we'll try to dlopen.
          This is complicated because on linux libintl is part of
          libc so there we must link directly. Further complicated
          because fink install script has a bug and doesn't put
          /sw/lib in DYLD_LIBRARY_PATH so we have to look there
          ourselves.</li>

          <li>Locale strings aren't required to contain an encoding
          (which the locale docs incorrectly call a charset).
          Michal Nowakowski points me to nl_langinfo which will
          give me the encoding even if not specified in the
          locale.</li>

          <li>Add pdf files to the standard format list for
          openfontdlg</li>
        </ul>
      </li>

      <li>14-Oct-2006

        <ul>
          <li>New translations: Greek, Simplified Chinese, German,
          Polish.</li>

          <li>Using the help command would generally crash
          fontforge on cygwin.</li>

          <li>Adobe uses the American spelling of diaeresis (that
          is dieresis), but some fonts contain glyph names with the
          European spelling. So add that as an alternate.</li>

          <li>If a bdf font contained an unencoded .notdef glyph,
          then we crashed.</li>

          <li>Adding Greek translations for font styles. (Thanks to
          Apostolos)</li>

          <li>If we aren't dealing with a TeX math font, then the
          "Sub/super"script positioning fields of Glyph
          Info-&gt;TeX aren't meaningful. So grey them out.</li>

          <li>Remove internal/external did the wrong thing in
          expand stroke if we also removed overlap and had
          counter-clockwise splines.</li>

          <li>Alexej Kryukov points out that reverting a glyph with
          anchors lost the anchors.</li>

          <li>Add simplified Chinese style names to our built-in
          lists.</li>

          <li>Problem reading autotraced input.</li>

          <li>The encoding change of last summer broke tfm output
          with glyph lists or extension characters.</li>

          <li>If add extrema added a point too close to a start/end
          point expand stroke could generate NaNs.</li>

          <li>FF could crash when adding extrema to an open
          contour.</li>

          <li>Add Polish styles to the translation list.</li>

          <li>Add a scripting function to set the gasp table.</li>

          <li>Add support for the 'gasp' table.</li>

          <li>Alexej Kryukov wants format 6 cmap tables.</li>

          <li>After editing instructions the debugger would
          incorrectly complain that instructions were out of
          date.</li>

          <li>Michal Nowakowski complains that "Instructions are
          out of date" warning appears too many times when doing a
          global transformation. Make it only pop up as a dlg once
          and thereafter occur as a LogError.</li>

          <li>If a font contained only space glyphs it could still
          be marked onlybitmaps and not allow outline
          generation.</li>

          <li>Show ATT did not translate scripts &amp;
          languages.</li>

          <li>Parsing an empty list of ttf instructions crashed
          Michael Zedler's machine.</li>

          <li>Make type1 generation use (essentially) the same
          subroutine mechanism as type2.</li>

          <li>Local subroutines were being freed twice in cff
          cid-keyed font generation.</li>

          <li>Removing an alternate unicode encoding (Detach
          Glyphs) was broken in some cases.</li>

          <li>FF failed to perform some simplifications on the last
          spline of a closed contour.</li>

          <li>Various fixes for Michal N.</li>

          <li>Add scripting interfaces to many of the ctype
          functions.</li>

          <li>Add a scripting interface to the 'size' feature, now
          that Adobe has finally decided what to do about
          'size'.</li>

          <li>Had the wrong title for kerning state machine
          dlgs.</li>

          <li>Redo the preference dlg.</li>

          <li>The two preference items, AlwaysGenApple, and
          AlwaysGenOpenType, were a bad choice on my part and have
          lead to considerable confusion. I mentioned some time ago
          that I would remove them if there were no objection.

            <p>There was no objection.</p>

            <p>I have now removed them.</p>

            <p>I also made the SetPrefs scripting function sort of
            work if the user tries to set one of these (it will set
            the appropriate flags in the default option set used by
            generate).</p>

            <p>The defaults of these flags were different on the
            Mac from everywhere else. This meant that a script
            could do different things on the Mac and on linux. That
            seems like a bad idea. I have changed things so that
            the default options setting for generate is always
            OpenType.</p>

            <p><strong>THIS IS AN INCOMPATIBLE CHANGE AND SCRIPTS
            ON THE MAC COULD NOW BEHAVE DIFFERENTLY.</strong></p>
          </li>

          <li>Patch from Michal Nowakowski to have ff number points
          after conversion to quadratic.</li>

          <li>Try to provide disambiguation for all strings "New"
          so that in languages where "New" must agree in gender
          with the thing being created translators will be
          happier.</li>

          <li>Remove the po/Makefile.in and redo the configure
          script to build it (so that I don't have to modify it
          each time I get a new language).</li>

          <li>Extend the knife tool so that if Meta (Alt) is held
          down it will move any spline it intersects (rather than
          cutting the spline).</li>

          <li>FF would crash if $HOME (the directory that is, not
          the environment variable) did not exist.</li>

          <li>I guess it makes sense that if ff read in a
          compressed sfd file then using a simple File-&gt;Save
          command (not Save As) should produce another compressed
          sfd file.</li>

          <li>When scaling a reference in otf output we had
          problems if the reference had more than one contour.</li>

          <li>If we deleted many glyphs from a font we are
          sometimes left with kern pairs pointing to things not
          worth outputting. Make sure we don't generate kerning
          info for them.</li>

          <li>Ligature carets were not being scaled by scale to
          em.</li>

          <li>Patch from mfabian at suse.</li>

          <li>If a user has a font with a glyph that is bigger than
          16*em-size (in many dimensions) and that user generates a
          tfm file, then warn him that the glyph can't be expressed
          in a tfm file and truncate the size to the biggest legal
          value.</li>

          <li>Attempt to mitigate the effects of X claiming to have
          a font when it doesn't.</li>

          <li>Saving CID keyed fonts would look at garbage memory
          for its encoding data if not saved from the biggest
          subfont.</li>

          <li>Add support for version 4 of the OS/2 table.</li>

          <li>If Interpretation was set in a font then when
          generating a 8/16 type cmap fontforge always went down
          the traditional chinese (big5) branch.</li>

          <li>MS has changed their indic shaping engine. It still
          uses the same features but they are applied differently.
          To disambiguate this change they have created a parallel
          set of script tags for the indic writing system.
          FontForge should recognize these and use them when
          appropriate.</li>

          <li>When Adobe first released fonts with a 'size' feature
          they did not follow the opentype specification. In August
          of 2006 they announced an incompatible change to bring
          fonts produced after that date in line with the
          specification. Unfortunately there are programs which
          depend on the old, broken format.

            <p>Legacy programs will not work when given a font in
            the correct format. New programs should be able to
            handle either correct or broken 'size' features.</p>

            <p>A few of Adobe's programs make use of the 'size'
            feature, and XeTeX does. I know of no others (besides
            font editors). Both intend to upgrade their programs...
            So this may be less of an issue than I initially
            feared.</p>

            <p>FontForge should now be able to read in a size
            feature in either format and gives the user the option
            of producing 'size' features in either format on
            output.</p>
          </li>

          <li>For Japanese fonts we tried to use cp932 (a variant
          of sjis) but then halfway through didn't know what to do
          with it.</li>

          <li>Another fix for saving sub-opentype fonts from a cid
          font.</li>

          <li>From a script, if a user asks to generate a ttf
          outline font with ttf bitmaps from a database with no
          outlines then technically this isn't supposed to work.
          But it used to and it's easy enough to tweak so that it
          works again.</li>

          <li><strong>Update to Unicode 5.0</strong></li>

          <li>Again when adding accents to the left of a glyph we
          should shift the glyph over to give it a reasonable
          lbearing.</li>

          <li>When building an accented glyph, we generally want
          use_my_metrics set on the reference. But if we add an
          accent to right (horn) or left (psili/varia on cap
          greeks) we want to turn it off. We did turn it off on the
          right side, but not on the left.</li>

          <li>Philipp Poll points out that ScaleToEm doesn't scale
          the OS/2 metrics (and some other stuff). Actually it
          does, but font info did the scaling BEFORE setting the
          values. So the metrics get scaled, and then reset to the
          values in fontinfo (which usually means they don't get
          changed).</li>

          <li>Fix some memory leaks.</li>

          <li>Some fixes for pcf loading.</li>

          <li>Various fixes to CID keyed fonts.</li>

          <li>Even the pretty ttf approximation routines need to
          worry about diametrically opposed control points.</li>

          <li>When generating multiple type1 fonts, output the
          bounding box of each as that of the full font. This will
          make it vaguely likely that applications will get the
          same line spacing.</li>

          <li>Oops. The vertical metrics bit wasn't preserved when
          flattening a cid font.</li>

          <li>Ack! Window titles and such were being interpreted in
          Latin1 and not in UTF-8.</li>

          <li>Interpretation of PostScript arc operator failed if
          the two angles were 360 degrees apart. Normalization made
          them both the same.</li>

          <li>Try to clean up bitmap only sfnt generation.</li>

          <li>pcf wasn't in the Open Font dialog format list (nor
          was pmf, nor pdf)<br />
          Add a filter for TeX bitmap fonts.</li>

          <li>Provide a mechanism (if a preference item is set) for
          picking a cmap when loading a font.</li>
        </ul>
      </li>

      <li>22-Aug-2006

        <ul>
          <li>Add a pane to the Preference dlg allowing user to
          control some of fontforge's hint creation.</li>

          <li>Someone complained that Find Problems-&gt;Path
          Direction got the wrong answer. It got the wrong answer
          because they had a self-intersecting path (which screws
          up all concepts of in/out-side. So try to make it clear
          that they should do a find intersecting paths first.</li>

          <li>Update my opentype scripts list (in particular
          include music).</li>

          <li>Due to a typo, ff thought pretty much everything
          outside unicode BMP was in the hebrew script.</li>

          <li>Add a new command to the point menu which allows you
          to specify a spline and one coordinate (either X or Y) on
          that spline. FF will calculate the other coordinate and
          add a point there.</li>

          <li>CODE2000 contains an anchor class with only base
          glyphs (no mark glyphs) as part of a set of anchor
          classes. FF crashed.</li>

          <li>Patch by Nix. svg.c did not compile when designed to
          be linked directly with libxml (instead of dlopening
          it).</li>

          <li>Redo the font open dlg so that there's a list of
          standard filters and a mechanism for changing that list.
          Remember the last filter used.</li>

          <li>If a popup menu is huge it used to appear under the
          cursor. This meant that even if the user didn't mean to
          s/he would have selected something and press/release
          would not be a no-op. This was a problem with the Font
          Info -&gt;TTF Names</li>

          <li>Patch from SUSE. Use of uninitialized local variable.
          But the result is never used, so just remove the
          offending lines.</li>

          <li>Emulate gtk's boxes and use that to do automatic
          dialog layout. Get the font info dlg working (and then
          several others too). This means that the layout is no
          longer optimized for English, but will look better in
          other languages (I hope).</li>

          <li>Add an information to Font Info to display what
          unicode character ranges are supplied by the font.</li>

          <li>Philipp Poll points out that when generating
          versioned fonts (ie. Ambrosia-1.0 rather than just
          Ambrosia) you don't want the filename to default to the
          fontname (the fontname will be Ambrosia), instead you
          want some way of specifying a default filename. So add
          that to the Names pane of the Font Info dlg.</li>

          <li>Try to keep track of font creation and modification
          times. NOTE: This is different from file times (which is
          what appears to be stored in the 'head' table of an sfnt
          file). Add a new table 'FFTM' to our sfnt output with
          these timestamps (and the timestamp of fontforge itself,
          just in case we ever care).</li>

          <li>Mark classes could not be set from the
          selection.</li>

          <li>Ben Laenen points out that if an order2 glyph has a
          dependent which refers to it using point matching and we
          keep changing the point number on the glyph then we'll
          keep getting warning messages. He suggests one
          message.</li>

          <li>Empty glyphs weren't marked with red Xs any
          more.</li>

          <li>In font compare, when comparing two
          contextual/chaining lookups, I forgot that class[0] was
          always NULL.</li>

          <li>Open contours caused the ttf point renumberer to
          crash.</li>

          <li>A font can have many kerning pairs. More than will
          fit in one GPOS subtable (which essentially has a 64k
          data limit or a bit more than 10,000 kern pairs). So be
          prepared to generate many sub-tables each dealing with a
          subset of the (first) glyphs.</li>

          <li>If an apple mutually exclusive feature had a default
          setting which wasn't 0 then my previous patch didn't
          work.</li>

          <li>If guessing bluevalues found no OtherBlues,
          fontinfo-&gt;PS Private would create an incorrect
          OtherBlues value [0]</li>

          <li>Support clipboards containing image/svg</li>

          <li>Ralf Stubner points out that the maximum zone size of
          bluezones is determined by 1/BlueScale. So adjust
          BlueScale if the max zone is too big.</li>

          <li>Merge fonts didn't merge anchors and got into a
          terrible mess. Let's merge kern classes and state
          machines too. Merging kern classes may be a bad idea. We
          don't really merge them we just copy them so that if the
          same glyph is mentioned in two classes unexpected things
          might happen.</li>

          <li>ff could crash on an sfd file containing erroneous
          anchors (such as might be generated by the merge fonts
          command).</li>

          <li>Once upon a time, Apple was so concerned about
          accuracy of floating point operations that they required
          all operations be performed in IEEE extended (80bit).
          This had the interesting side effect that a program which
          conformed to Apple's standards could not also conform to
          ANSI C (which required operations use double temporaries
          for double values). I find it somewhat ironic, therefore,
          that gcc on the mac doesn't even promote floats to
          doubles. FF needs the extra accuracy provided by a double
          (an extended type doesn't seem to provide additional
          assistance unfortunately). So on the mac we got extrema
          that weren't, which meant that remove overlap
          didn't.</li>

          <li>If we had a mac feature which had multiple subtables
          (ie. a state machine for a contextual substitution, and a
          non-contextual substitution too) then we produced a bad
          chain in the morx table.</li>

          <li>Merge &amp; Simplify would sometimes generate
          solutions using control points which were diametrically
          opposed to what they should be.</li>

          <li>Yet another attempt to do a better job of
          autohinting.</li>

          <li>Add a "Revert to Backup" command.</li>

          <li>Put code in to correct for single bit (sometimes
          double bit) errors when search from extrema. This is at a
          lower level than the previous patch.</li>

          <li>Output of extension lookups wasn't working</li>

          <li>Fixed a problem in the ttf names pane of Font
          Info.</li>

          <li>A slight improvement to magnifying by dragging a
          rectangle.</li>

          <li>The first time you click on a transition in a Font
          Info-&gt;Mac SM-&gt;Indic state machine, ff would
          crash.</li>

          <li>Tihkomirov points out that it isn't clear how to
          delete a ttf name from the name pane of fontinfo. So add
          some popup help. The language &amp; string ID menus in
          that pane were sorted on the wrong key</li>

          <li>Was not preserving (unparsed) tables properly.
          Several bugs.</li>

          <li>When loading an apple bitmap font (with no hmtx
          tables) we need to dummy up widths for the outline
          glyphs.</li>
        </ul>
      </li>

      <li>15-Jul-2006

        <ul>
          <li>Apple's bitmap only fonts should not have an 'hhea'
          nor an 'hmtx' table<br />
          Dummy up outline glyph widths when we don't have a 'hmtx'
          table by looking at bitmap widths for that glyph.<br />
          ftxvalidate complains if the vertical line metrics are 0.
          Even in a strike with no vertical metrics information. So
          dummy something up.</li>

          <li>Was getting the flags wrong for turning off features
          in an apple morx chain.</li>

          <li>When outputing mark-to-base sub-tables with multiple
          marks I neglected to output an NUL offsets for the
          anchors that weren't there. So if a glyph had only one
          anchor (instead of two, or however many) then the offsets
          would be all wrong.</li>

          <li>The SetPref() scripting function was misdocumented to
          be called SetPrefs() so accept both names.</li>

          <li>When building an accented letter out of glyphs with
          an anchor class ff would increase the advance width of
          the accented glyph by the size (xmax-xmin) of the
          accent.</li>

          <li>Expand the functionality of the ruler tool so that it
          also shows curvature.</li>

          <li>When importing a bitmap font from a mac binary or an
          sfnt and the encodings of the destination and the bitmap
          did not match, then things got rather screwed up and
          might crash.</li>

          <li>patch from KANOU. the ref check routine in glyphcomp
          compared one reference to itself.</li>
        </ul>
      </li>

      <li>03-Jul-2006

        <ul>
          <li>Type2 charstrings have no closepath operator. I used
          to think that meant I could not omit the final vector. In
          fact it means I can omit the final vector AND the
          closepath operator.</li>

          <li>If we had a font with no complete code pages we used
          to generate a version 0 OS/2 table without codepage info.
          But now windows refuses to install such a font. Instead
          generate a bogus codepage field which claims to have
          latin1 (even though it doesn't).

            <p>Windows won't use a font where the codepages field
            is 0.</p>
          </li>

          <li>When generating a FOND for a bitmap only sfnt, we
          created dummy 'NFNT' resources with the wrong resource
          ids. Which meant we got garbage when the font was
          used.</li>

          <li>Make the TabSets in the font &amp; glyph info dialogs
          run vertically rather than hor izontally. (Add an option
          to get the old display back).</li>

          <li>Approximate Spline from Point Slopes sometimes set
          the control point while leavi ng the nonextcp flag
          on.</li>

          <li>Add Extrema only looked at how close a point was to
          the extrema in one dimension. While that dimension is
          more important, make a less stringent check on the
          other.</li>

          <li>Expand Stroke removes "U-turns" from splines because
          they confuse it. But the routine that did that got a bit
          rambunctious and did the wrong thing on a circular
          arc.</li>

          <li>If a font did not contain an OS/2 table then we
          didn't retain the 'hhea' ascent/ descent.</li>

          <li>Various fixes from Matthias Kilian of OpenBSD.</li>

          <li>When asking for default 'subs' features, every glyph
          gets assigned U+2080.</li>

          <li>Display the curvature information at each point. In
          Point Info dlg, and in a pop up window when editing
          cps.</li>

          <li>Add two new menu commands/scripting commands:

            <ul>
              <li>Canonical Start Points (CanonicalStart())</li>

              <li>Canonical Contours (CanonicalContours())</li>
            </ul>

            <p>The first sets the start point of each contour to
            the leftmost point, while the second orders the
            contours by their leftmost points. This will slightly
            reduce the size of output charstrings. It will also
            make more things available to be put in
            subroutines.</p>
          </li>

          <li>Print Multi-Size &amp; Full Page printed the wrong
          glyphs from the font view. Broken since the encoding
          change.</li>

          <li>When stroking a contour that makes a 180degree turn,
          ff did not give it a semi-circle if linejoin was set to
          round.</li>

          <li>SPLCopyTranslatedHintMasks didn't work if there were
          more than one contour being copied.</li>

          <li>Nathan Summers points out that if the XUID is garbage
          the ff can go into an infinite loop when generating an
          otf/cff font.</li>

          <li>Somehow the XUID and UniqueID fields crept off the
          bottom of the fontinfo Names p ane and weren't visible or
          modifyable. Give them their own pane now.</li>

          <li>Apply some patches (with some changes) from Nathan
          Summers to the truetype debugger.</li>

          <li>The property count in BDF fonts is wrong.</li>

          <li>Ralf Stubner points out that the notdef glyph in an
          otf font should look like that in a ttf font, and not
          like that in a type1 font. (that is there should be
          something in the glyph).</li>

          <li>Add support for group "encodings" which have empty
          spaces for unused glyphs.</li>

          <li>make another attempt to find a good default sli for
          glyphs with no default script.</li>

          <li>Typo in scripting function DefaultATT.</li>

          <li>The View-&gt;Display Substitutions has been broken
          since the encoding change last summer.</li>

          <li>Mark glyphs with out of date instructions differently
          from those with no instructions.</li>

          <li>The last change to the cvt table generally did not
          get made.</li>

          <li>Make glyph compare check for point matching in anchor
          points and in references.</li>

          <li>Add a warning message about out of date instructions
          when generating a font.</li>

          <li>When generating a font with anchor points matched to
          ttf points, ff failed to allocate enough space for them
          and offsets got all confused.</li>

          <li>Oops. Some variables which should have been static
          were dynamic. Which meant we kept dlopening
          libfreetype.</li>

          <li>If we had an anchor point which positioned itself
          with point matching, and we ge nerated an otf font then
          we'd output a lookup which tried to do point matching i n
          postscript. Only do point matching if we are sure we're
          in a tt font.</li>

          <li>Add a preference item to control clearing of tt
          instructions.</li>

          <li>Printing a multi-size page of a truetype font
          crashed.</li>

          <li>Anchor Point dlg didn't work well with matching tt
          points.</li>

          <li>Add a field to allow users to search for a glyph name
          within a kerning class.</li>

          <li>Interesting. In kerning by classes, if the coverage
          table does not match the glyphs specified in all the
          classes (for the first (left) glyph), then any glyphs in
          the coverage table but not in any class should be treated
          as being in class 0.</li>

          <li>Add something to the font view's copy from menu to
          control whether truetype instructions are copied or
          not.</li>

          <li>Add some more problems to find problems

            <ul>
              <li>Check for glyphs with both contours and
              references.</li>

              <li>Find out of date point matched references.</li>

              <li>Find references with transformation matrices
              which can't be expressed (as refs) in truetype</li>

              <li>Find references with transformation matrices
              which aren't translations (and so can't be expressed
              (as refs) in type1/2 fonts.</li>
            </ul>
          </li>

          <li>Allow the user to turn off composite info in afm
          files.</li>

          <li>otf kerning classes were dumped in the wrong
          order.</li>

          <li>In GaramondPremrPro.otf (version 001.000) Adobe has
          coverage tables (for some context chaining subs) which
          have the glyphs mentioned multiple times. I suppose this
          is legal, but it is annoying. I want my strings to have
          each glyph appear at most once. So add a little thingy to
          remove duplicate glyphs when we generate a list of glyph
          names.</li>

          <li>Adobe has deprecated the use of PUA to represent
          small caps, old style numerals, etc. Add a preference
          item so that ff will no longer recognize "a.sc" as having
          a PUA encoding.</li>

          <li>The tool tip for the preference item
          "NameListForNewFonts" was wrong.</li>

          <li>Horizontal scrolling in the show att dlg was too
          slow. It was by pixel. Make it be by something which
          approximates the width of a character.</li>

          <li>Add a new scripting command to give a font's bounding
          box.</li>

          <li>Sigh. Within a GPOS lookup, sub-tables are not
          additive. Only one will be applied at a time. So order
          the 'kern' lookup so that pair-wise kerning comes out
          first (to override class kerning).</li>

          <li>Was sometimes outputting mkmk base-mark attachement
          points as the mark attachment point.</li>

          <li>Clytie Siddall has many suggestions about how to make
          the translation process easier for translators. He also
          tells me how to insert contextual comments into the
          program source, and provides many fixes for typoes.</li>

          <li>The OS/2 version 1,2 has a different defn of
          avgCharWidth than OS/2 version 3(,4) does. Display of CJK
          fonts is supposed to break under windows if using the v3
          defn.

            <p>Use the appropriate defn for the version we happen
            to be outputting.</p>
          </li>

          <li>Autohinting crashed on glyphs in an order2 font if
          the glyph contained both an outline and a reference.</li>

          <li>Pressing the help key in the main windows went to the
          overview page, not to the contextual help for the
          window.</li>

          <li>Add a warning when 'CFF ' widths and 'hmtx' widths
          differ (when loading a font).</li>

          <li>Set the default and normative widths too late after
          the cff subroutine change.</li>

          <li>Make double clicking in the list of kern pair/anchor
          combinations bring up either Kern Pair Closeup dlg or
          Anchors Away.</li>

          <li>The Anchor control dlg didn't work after the encoding
          change.</li>

          <li>Add a popup message to explain what "Cor:"
          means.</li>

          <li>Doing a Close() from a script didn't work if the
          windowing system were open.</li>

          <li>Yet another bug in type1 hinting output.</li>

          <li>Some versions of realloc don't like allocating 0
          bytes.</li>

          <li>Users expect ff to recognize a glyph name
          "Diaeresis", even though Adobe (following standard
          American, but not European spelling) spells it
          "Dieresis".</li>

          <li>GhostScript has canniptions when it gets a version 3
          OS/2 table in a ttf file.</li>

          <li>Can't add a flex hint when there's a hintmask at the
          mid point.</li>

          <li>The hintmask part of PointInfo would not let you
          clear a hintmask.</li>

          <li>Add a new command to the fontview:
          Edit-&gt;Select-&gt;Select by Name<br />
            and a new scripting command: SelectAllInstancesOf

            <p>Both will select all encoding slots containing the
            named glyph (or unicode value)</p>
          </li>

          <li>Add scripting command: RemoveDetachedGlyphs</li>

          <li>Was setting typo linegap to hhead linegap.</li>

          <li>Using the X clipboard to paste into the character
          view has been broken at least since I added multi-layered
          editing.</li>

          <li>Add a pref to control whether we prefer to use
          spacing or combining accents when building accented
          glyphs.</li>

          <li>Spacing in the group dlg was sometimes off.</li>

          <li>More hinting fixes. If the edges of a stem aren't
          quite parallel we had problems</li>

          <li>Add some new built in variables: $order, $em,
          $ascent, $descent</li>

          <li>The 'TeX ' table was output incorrectly if glyph's
          order wasn't the same in the sf as in the ttf.</li>

          <li>Allow the [*] Back visibility checkbox to control
          whether the grid fit lines are visible or not.</li>

          <li>If scripting is in verbose mode, flush the output
          buffer before calling a built in procedure (so any errors
          it generates will at least show the right line).</li>

          <li>Ambrose LI points out that the master font in a cid
          keyed font should match the ascent/descent of at least
          one of its subfonts (so that the typoAscent/Descent f
          ields will default correctly).</li>

          <li>Spend some quality time with valgrind looking (oh,
          and fixing) memory leaks.</li>

          <li>Make ControlAfmLigatureOutput (scripting command)
          apply to ofm/tfm files too.</li>

          <li>Oops. When parsing mac state machines I was using
          sizeof(long) when I should have said sizeof(int32). It
          gave rather bad results on 64bit machines.</li>

          <li>Add a scripting function to load a user defined
          cidmap file.</li>

          <li>Hmm. sizeof(point)==8 on AMD64, but structures are
          aligned to 4. This means our chunk alloc routines
          complain. So if we're given something that isn't in units
          of sizeof(pointer) then just round it up.</li>

          <li>lookup ordering within GSUB has been totally broken
          at least since I added the code to coalesce lookups for
          kerning.</li>

          <li>Kanou suggests changing function name that includes
          Char to be Glyph. Well a few do really mean Char, but the
          rest should be Glyph. Leave the old names there bu t
          document them as deprecated.</li>

          <li>Make CID keyed fonts use the new subroutine mechanism
          too. We can use global subrs now too!</li>

          <li>Oops. Familyname can be NULL, and we were
          indescriminately checking to make sure its length was
          less than 31.</li>

          <li>Make a better use of subroutines when generating otf
          fonts. Doesn't work for CID fonts yet.</li>

          <li>We crashed if we changed from one cid sub-font to
          another when compacted.</li>

          <li>Oops. I made ff work with ft22 if the debugger was
          being built... but it failed to compile if people didn't
          build the debugger.</li>

          <li>Oops a scripting function was marked as not needing a
          font when it did (HasPreservedTable &amp; friends).</li>

          <li>More for font compare. If there is a difference in a
          glyph in the two fonts add the option for including the
          outlines of the second glyph into the first. If the first
          font is missing a glyph, add an option to insert it with
          the outlines in the background.</li>

          <li>Good heavens, someone wants to play with acorn2sfd.
          Make it compile again.</li>
        </ul>
      </li>

      <li>08-Apr-2006

        <ul>
          <li>Patch by Mike Frysinger from gentoo. Use the HOME
          environment variable in preference to /etc/passwd.</li>

          <li>Werner wants to see raw data in the points window of
          the debugger. My guess is that most people won't be
          interested in this mode (and it makes the window a bit
          uglier) so I've made it configurable.
          --with-debug-raw-points</li>

          <li>Write sfddiff as a fontforge script and put it back
          into the install process.</li>

          <li>Add code to font compare so it can do the old sfddiff
          --merge option (if two corresponding glyphs differ, add
          the outlines of the second to the background of the
          first).</li>

          <li>Someone wanted acorn2sfd! Make it compile again.</li>

          <li>Make configure look for libgif</li>
        </ul>
      </li>

      <li>06-Apr-2006

        <ul>
          <li>Patch by Ian Jackson of Ubuntu. When in an empty
          glyph (one not WorthOutputting) then doing a
          View-&gt;Show Grid Fit would cause a crash.</li>

          <li>The PLRM says that formfeed is whitespace. The
          T1_Spec says that it is not. After an eexec the T1_Spec
          is right (and ff was following the PLRM
          definition).<br />
          Also add a check to insure that the first character we
          generate in pfb encryption isn't a white space
          character.</li>

          <li>On some windows systems (mine at least), windows will
          refuse to install a postscript font if the fontname or
          familyname of that font is longer than 31 characters.
          These are the names in the Font Dictionary of the
          postscript font itself, not the names in the 'name' table
          (for otf fonts).</li>

          <li>Make ff compile with freetype 2.2.0</li>

          <li>The popup menu of text fields was garbage.</li>

          <li>Make a change to pfm output which might allow non
          windows ANSI encoded fonts to work.</li>

          <li>Allow the freehand tool to work in quadratic
          fonts.</li>

          <li>Didn't always refigure splines properly when using
          Get Info in quadratic mode. Patch by Michal
          Nowakowski.</li>

          <li>Trying to invoke the KDE browser (for help) didn't
          work. Patch by Dimitar Zhekov</li>

          <li>Still losing instructions if contours begin with
          off-curve points.</li>

          <li>if a font had a defined notdef glyph, then FF would
          usually enter it incorrectly in the 'hmtx' table.</li>

          <li>In the Select menu, Width had an extra
          underscore.</li>

          <li>Wasn't looking in the right place to get the right
          weight name in an otf font.</li>

          <li>People have been complaining about the UI for drawing
          quadratic (truetype) curves. It was consistent with the
          UI for drawing cubic (postscript) curves, but it seems
          hard to draw quadratics that way. Rather than
          concentrating on the on-curve points (as in cubics), now
          concentrate on the off-curve points. So the pen-tool
          behaves quite differently now in quadratic mode. As does
          Element-&gt;Get info.</li>

          <li>A patch added back in 2004 to make vertical
          substitutions work for Japanese (to work around a bug in
          Windows to be precise) had a bug itself if more than one
          language was involved.</li>

          <li>When outputting an inline copy of a reference in otf
          fonts with translated hintmasks we did the wrong
          translation for vertical stems and got garbage
          results.</li>

          <li>New command to allow user to enter X,Y coordinates of
          a point and have that point be selected. I want this for
          debugging. It might be useful generally.</li>

          <li>Fixed problems with type2 subroutines containing
          glyphs with conflicts.</li>

          <li>ReplaceWithReference had too large a fudge factor and
          found macron when it should have found macron.sc in
          minionpro-regular.</li>

          <li>If an alternate/multiple subs had more than 30
          components then we lost all those after 30 when
          generating opentype GSUB table.</li>

          <li>Hmm. Sometimes least squares does give the answer we
          want for merge. So give it a try.</li>

          <li>Patch by kanou to fix some translation problem.</li>

          <li>In the shape tools (round rect, ellipse): Instead of
          generating a quadratic shape at the start, generate a
          cubic shape and convert to quadratic. The convert routine
          now knows about how to find integer control points and
          such.</li>

          <li>Patch from Kanou to get more grid size values for
          looking at bitmaps.</li>

          <li>If a glyph starts with a control point then ff would
          sometimes throw out the ttf instructions, thinking it
          wasn't numbered properly.</li>

          <li>A merge in a quadratic font produced a straight line.
          Even when it shouldn't have.</li>

          <li>Change namelists to support non-ASCII glyph
          names.</li>

          <li>Oops. Some hinting scripting commands had a "b"
          prepended to their name by mistake. Sigh. From now on
          support both names.</li>

          <li>When pasting a glyph with hints into an empty glyph,
          we shouldn't set the "in need of autohinting" flag.
          (Actually, we might should if the original copy were done
          in a glyph with out of date hints.... but that gets more
          complicated).</li>

          <li>Patch to make loading bdf fonts more efficient.</li>

          <li>Add Kanou's "fontview" font to the list of fonts
          searched by default for the fontview window.</li>

          <li>FF did not mark ghost hints as different from normal
          hints.</li>

          <li>Interpolating fonts broke when I did the encoding
          change last summer.</li>

          <li>Patch from Kanou to prevent the hash function from
          returning negative numbers. (and crashing)</li>

          <li>Add a menu and a scripting command to compare two
          fonts.</li>

          <li>Oops. There's a stray underscore in a field in font
          info.</li>

          <li>Refresh font view(s) after changing glyph
          name/unicode in glyph info in case those are being
          displayed.</li>

          <li>If a name entered in the goto dlg was a single
          unicode char, then goto would treat it as such. Normally
          this is fine, but a user might use the underscore
          character (for example) as a glyph name and not assign it
          to U+005F. So check for the name too.</li>

          <li>Rewrite the cubic-&gt;quadratic conversion code. It
          now looks much prettier and tries to position
          intermediate points on integer (or half integer)
          locations so there won't be unexpected rounding later.
          It's slightly less accurate though.</li>

          <li>Many changes to the postscript hinting code.</li>

          <li>If a glyph contained references but no alphabetic
          characters then Glyph Info would crash.</li>

          <li>Scripting command AskUser doesn't work unless
          FF_SCRIPT_IN_LATIN1 is set. Patch by Kanou.</li>

          <li>In some error messages I ended a sentence with a
          comma. Make it a full stop.</li>

          <li>Patches from Kanou to make Japanese translation
          better.</li>

          <li>Kanou points out that the code which handles
          modifications to the unicode char textfield (in glyph
          info) complains about the wrong things and he provides a
          patch.</li>

          <li>Hand tool failed to scroll background images
          (probably failed on hints too).</li>

          <li>When doing a copy splines with hintmask operation we
          neglected to refigure the spline after transforming the
          end points. This was ok since we never used that info --
          except if the splines were quadratic and we needed to
          convert to cubic. So when generating a ps font from a
          quadratic database, and the font contained references
          with scaling/rotation/etc. then we'd get erroneous
          results.</li>

          <li>In Find Problems, the Flipped Reference check could
          fail if the reference contained a contours which
          intersected (themselves or each other).</li>

          <li>Make ff aware of ExtraLight as a valid weight when
          setting a default value for the PS weight string.</li>

          <li>When the user clicked on a textfield with attached
          pulldown list, ff would get an event saying the first
          entry on the list had been chosen. This meant that the
          Tag dialog (used for new ligatures/substitutions/etc.
          would show the first tag in the list instead of
          blank.</li>

          <li>Include some glyph name synonems from Richard Kinch's
          TrueTeX list.</li>

          <li>Determination of whether a ghost hint is top (-20) or
          bottom (-21) should depend on the current contour, not on
          the glyph as a whole.</li>

          <li>If a glyph consists solely of references then add
          _&lt;ref-name-1&gt;_&lt;ref-name-2&gt;...&lt;ref-name-n&gt;
          to the list of possible names. Sometimes also add
          uniXXXXXXXX.</li>

          <li>Kanou wants to translate some more strings.</li>

          <li>Barry.SCHWARTZ wants to be able to reencode a font to
          compact from a script.</li>

          <li>Barry.SCHWARTZ points out that my "cfg" files contain
          no newlines. Shows how much use they've received:-)</li>

          <li>Barry.SCHWARTZ points out that when generating an afm
          file for an otf font only the first 256 characters were
          given encodings.</li>

          <li>Simplify much improved.</li>

          <li>Make simplify for quadratic splines aware of the
          peculiarities of truetype. So one simplification is to
          make a point interpolateable. And removing a point is not
          always good if it means points that were interpolateable
          become non-interpolateable.</li>

          <li>After examining (and stealing with permission) Huw
          Davies's code in wine/tools/fnt2fon.c I believe I can now
          produce .fon files.</li>

          <li>Add support for reading bitmap references (from an
          sfnt bitmap)</li>

          <li>Patch by Kanou. cvknife didn't compile in one
          mode.</li>

          <li>Typo in an error message</li>

          <li>Add a command to show points of inflection (also
          change View-&gt;Mark Extrema to show where extrema occur
          on a spline if not at the endpoints)</li>

          <li>Patch by Michal Nowakowski. Uninitialized variable in
          simplify dlg.</li>

          <li>glyph names for unencoded glyphs were always
          "uniFFFFFFFF" should be "NameMe-&lt;n&gt; broken by last
          summer's encoding changes.</li>

          <li>Werner wants CC (composite character) entries in afm
          for GPOS mark-to-base features.</li>

          <li>The switch to utf8 last summer broke font
          info-&gt;Size</li>

          <li>Allow users to ask for both 'GPOS' and old-style
          'kern' tables. FontLab does this. The OpenType list is
          generally disapproving of the idea.</li>

          <li>If we tried to put more than about 10000 kerning
          pairs into one old-style kerning sub-table then we'd
          overflow various shorts. So split it up after about 10000
          kp into several different sub-tables.</li>

          <li>Round to Int screwed up interpolated points.</li>

          <li>When generating a tfm file don't generate a width
          bigger than 16*em-size (even if the font says to) because
          TeX will throw it out.</li>

          <li>Alexey Kryukov's patch to fix an error message.</li>

          <li>Printing a CID keyed truetype font to a pdf file
          produced a very odd ordering of glyphs (compacting some
          and omitting others and getting errors when it ran out of
          glyphs but asked for more).</li>

          <li>Alexey Kryukov suggests repunctuating an error
          message.</li>

          <li>Johan Winge suggests an improvement to converting
          cubic splines to quadratic: If we end up using a line
          when looking at the spline as a whole, try breaking it at
          the point(s) of inflection first. It seems like a good
          idea.</li>

          <li>Johan Winge also points out that I identify points as
          tangents when they should not be. This is because I use
          one measure of sloppiness no matter how close the cps are
          to the base point when determining collinear. It's
          probably best to have a variable measure depending on how
          far the cp is from the base point.</li>

          <li>Alexey Kryukov thinks Add Unencoded Slots should work
          in the compacted view by making the thing have a custom
          encoding.</li>

          <li>Scripting reencode didn't get rid of the "compacted"
          mark.</li>

          <li>Ralf Stubner points out that I produce type1
          charstrings which end in "seac endchar" when a simple
          "seac" is sufficient. He's right.</li>

          <li>When generating opentype tables in from a single
          sub-font of a cid-keyed font (ie. user asked for a ttf
          font generated from one sub-font) ff would crash.</li>

          <li>We didn't hint bold fonts well (anything where stems
          were bigger than em-size/10)</li>

          <li>When generating a type1 font with a glyph containing
          a reference that had to be unlinked, then the vertical
          stems in that reference would not be hinted.</li>

          <li>When guessing points at which to attach hints in
          type1/2 read in we failed if the points were too widely
          spaced. Be a bit more lenient.</li>

          <li>SetCharName didn't check its flag value
          properly.</li>

          <li>Uncompacting a font caused memory problems.</li>

          <li>Fix simple crash in metafont.</li>

          <li>When importing unencoded glyphs into an already
          existing font, we would sometimes fail to find the
          matching glyph (and would create a new one).</li>

          <li>If a font contain an encoded glyph called ".notdef"
          and that glyph was not the first glyph, then type1 fonts
          had a .notdef glyph at a random place in the font. Now
          freetype seems to renumber glyphs so .notdef is always
          glyph 0 which fontforge did not expect and produced some
          strange results when rasterizing (tested on 2.1.10). Fix
          is simple: always make notdef be first in the chars
          dictionary and then all is happy.</li>

          <li>Add new scripting command to compare two glyphs. I
          want this for testsuites, other people might find a use
          for it.</li>

          <li>gniibe reports that the scripting function Export()
          produces bitmap images with the wrong format and provides
          a patch.</li>
        </ul>
      </li>

      <li>9-Feb-2006

        <ul>
          <li>Instead of refusing to do expand stroke/remove
          overlap for order2 fonts, why not convert the contours to
          order3, do the function and convert back.</li>

          <li>Once more we are numbering points badly.</li>

          <li>If we clear a glyph which is being referred to (and
          we don't unlink it first) then when we save it into an
          sfd file we get a reference to a glyph at orig_pos -1
          (because the cleared glyph isn't stored in the sfd) which
          causes an error when reading it back in.</li>

          <li>If a copyright message were an exact multiple of 100
          characters long, fontforge would screw up memory (and
          potentially crash) when reading it in from an sfd
          file.</li>

          <li>The Merge/Simplify command (which Add Extrema now
          calls) had problems when the control points were very
          close to the base point so that the point was (to the
          human eye) a corner point.</li>

          <li>Add support for the r2l script N'Ko. MS says opentype
          will use script 'nko ', ISO says the tag should be
          'nkoo'. Follow opentype.</li>

          <li>Kanou tells me that Syriac &amp; Thaana are also r2l
          scripts and should be added to my list.</li>

          <li>If FF was given multiple fonts on the command line
          the sizes of the font windows would jump around in a very
          peculiar fashion.</li>

          <li>Add the concept of a namelist. Users can specify what
          names they want for new glyphs, or can force an entire
          font into a new naming scheme. Changes to

            <ul>
              <li>FontInfo</li>

              <li>Open</li>

              <li>Generate (Family)</li>

              <li>Preferences</li>

              <li>and the Encoding menu.</li>

              <li>New scripting functions:

                <ul>
                  <li>LoadNamelist(filename)</li>

                  <li>LoadNamelistDir([dir])</li>

                  <li>RenameGlyphs(namelist)</li>

                  <li>Extended Generate (scripting) to take a
                  namelist argument.</li>
                </ul>
              </li>
            </ul>
          </li>

          <li>If users didn't have libuninameslist installed we
          were still generating spurious ligatures for numero and
          TM. (and others)</li>

          <li>KANOU points out that if you comment out a bdf glyph
          (with COMMENT) fontforge sort of reads it anyway.</li>

          <li>Kanou needs to distinquish between the script latin
          and the language.</li>

          <li>SplineRemoveAnnoyingExtrema1 got tweaked a little too
          much in attempting not to generate insane control
          points.</li>
        </ul>
      </li>

      <li>25-Jan-2006

        <ul>
          <li>If you try to create a bitmap only sfnt but provide
          pixelsizes for no valid bitmap strikes, the fontforge
          would crash.</li>

          <li>Chia points out that I should use the PIXEL_SIZE
          property to set a bdf font's pixelsize (instead of using
          font ascent+descent).</li>

          <li>Trying to rasterize a glyph with a coordinate of 1e7
          caused a crash.</li>

          <li>The change to make Add Extrema remove points near the
          extrema failed to consider the possbility that some of
          those points might be corner.</li>

          <li>In Gentium Roman, when searching for bluevalues, the
          baseline is further than 1 standard deviation from the
          mean of glyph ymin. Change the range searched so that 0
          is always included.</li>

          <li>In Font Info-&gt;PS Private, if we selected
          OtherBlues and pressed [Guess] it did not change the
          OtherBlues value.</li>

          <li>The gettext patch changed Histograms-&gt;Blue Values
          menu item into a line.</li>

          <li>When changing the order of a font, ff would ask if
          you minded losing the undoes. There's no point in asking
          the question if the font hasn't been modified (it has no
          undoes).</li>

          <li>The Point Info dlg should enforce that curved points
          cps are collinear (so if the user changes one cp, the dlg
          should change the other to be in the opposite
          direction.</li>

          <li>There was a path though PointInfo that called
          SplineRefigure3, which meant that splines got marked as
          cubics even when they should have been quadratics.</li>

          <li>Using a rotated elliptical pen in expand stroke did
          not work</li>

          <li>Add a homedir button to the file chooser
          dialogs.</li>
        </ul>
      </li>

      <li>17-Jan-2006

        <ul>
          <li>Make the Import() scripting command accept
          {bdf,pcf}.gz files</li>

          <li>Reading utf7 (ttf name) strings from an sfd file was
          broken if one of the characters had bit 15 (high bit) set
          and its position in the string mod 3 was 1.</li>

          <li>My horizontal line metrics in the sfnt bitmap strike
          header were incorrect</li>

          <li>Use the horizontal line metrics (if they work) to set
          the ascent/descent of a bitmap strike.</li>
        </ul>
      </li>

      <li>15-Jan-2006

        <ul>
          <li>The change to fold all COMMENTS into one bdf property
          broke the sfnt 'BDF ' table routines.</li>
        </ul>
      </li>

      <li>14-Jan-2006

        <ul>
          <li>Change AddExtrema so that if an extremum is very
          close to an old point it will add the extremum and then
          remove the old point.</li>

          <li>Redid how bdf properties were handled

            <ul>
              <li>I had the definitions of some properties slightly
              wrong</li>

              <li>I was generating some obsolete properties</li>

              <li>When I generated CHARSET_ENCODING for iso8859
              encodings I had an extraneous "-" in the value.</li>

              <li>retain the properties when loading a bdf, pcf
              font</li>

              <li>Add a dialog which gives user control over bdf
              properties</li>

              <li>design a 'BDF ' table for SFNT files which can
              contain bdf properties and make FontForge read and
              generate this table.</li>
            </ul>
          </li>

          <li>Ted Packard points out that I output "big metrics" in
          sfnts inconsistently. This patch should make them
          consistent and right.</li>

          <li>Restore "compact" views to their old glory. Ie. they
          can now be uncompacted (and uncompaction happens
          automagically when generating a font).</li>

          <li>When reading a GenTags: line from an sfd file stored
          with CRLF line terminators, the next line would be
          lost.</li>

          <li>ff couldn't handle xrefs which were broken in bits in
          pdf files?</li>

          <li>When reading a ttf font from a pdf file we found no
          encoding info. This caused us to crash because various
          routines expected an encoding map. Add a dummy (Original)
          map if not exists.</li>

          <li>Wasn't numbering points in references properly.</li>

          <li>Gleep! Ever since the gettext code went in, the
          Generate fonts dlg has refused to generate "No Outline
          Font" and "No Bitmap Font".</li>

          <li>Herbert Duerr from OpenOffice tells me that their
          OpenSymbol.ttf font when produced by fontforge does not
          work on Win98. This is because Win98 doesn't like the
          codepages bits ff produces and refuses to use any glyphs
          in the font. He submitted a patch to make ff produce a
          version 0 OS/2 table (with no codepage info) for this
          font. Win98 will accept it then. His patch was against an
          earlier version of ff and needed to be modified for the
          current version.</li>

          <li>Patch by Raph Levien which finally shows me how to
          use FT_Outline_Get_Bitmap properly.</li>

          <li>If the user has never called PrintSetup (or if the
          user has not called PrintSetup this session and has not
          loaded prefs), then fontforge will invode setpagedevice
          on a pagesize which will fit on either A4 or US-Letter.
          The PS manual says a printer should refuse such a size
          unless it has paper within 5 points of it. So on printers
          which follow the spec (not mine) nothing will print as it
          waits for paper.

            <p>Now if the pagesize has not been set, don't specify
            a PageSize to setpagedevice.</p>
          </li>

          <li>The PrintSetup scripting command should not require a
          font.</li>

          <li>Add a mechanism so that users can prevent ff from
          making a point implicit. Useful in that point needs to be
          instructed.</li>

          <li>New copyright notices for 2006</li>

          <li>Make the pen tool work better with quadratic splines
          (make it default to having control points which cause the
          point to be implicit).</li>

          <li>Order2 elipses were not drawn accurately.</li>

          <li>Point numbers sometimes didn't get properly
          renumbered after changes. If we have references &amp;
          splines in a (truetype) glyph then show the numbers as
          "?".</li>

          <li>When a charview displays numbered (truetype) points,
          then it shows all the control points. But the control
          points are not selectable. This is not a good thing, so
          make them selectable.</li>

          <li>The font display to pdf did not include a title at
          the top of each page.</li>

          <li>Peter Denisevich points out that when we print
          something we say "%%Pages atend" instead of "%%Pages
          (atend)". And the latter is correct.</li>

          <li>Werner points out that my type1 (and type1 cid) fonts
          contain a %%DocumentSuppliedResource line, and they
          should not. The next level up should do that when it
          includes the font.</li>

          <li>Show .xpm files as images we support in import image
          dlg. We've always supported them, might as well show
          them.</li>

          <li>Check the glyph class when deciding what anchor to
          use.</li>

          <li>Anshuman Pandey wants to be able to set the glyph's
          GDEF class. I've never understood why the default
          behavior wasn't good enough, but it's easy to do.</li>

          <li>One of the fields in Glyph Info had some garbage
          initialization.</li>

          <li>Add a default anchor point type to the AddAnchorPoint
          scripting command. FF will try to guess an appropriate
          value.</li>

          <li>Add some standard window sizes to the fontview
          window. I'm tired of having the windows sized to other
          people's standards whenever I review a bug.</li>

          <li>There was a path through expand stroke where a
          control point was marked as non-e xistant by
          mistake.</li>

          <li>Expand Stroke would leave contours with the reversed
          orientation if it had to do a remove overlap
          internally.</li>

          <li>Oops. The routine to save the encoding prefs file
          could not handle an encoding plug-in.</li>

          <li>KANOU points out that the origin pulldown list in the
          transform dlg was not being translated.</li>

          <li>In the preference dlg all of the [...] file browsers
          had the title "Call Script" which isn't appropriate for
          most of them.</li>

          <li>Typing .* and pressing [Filter] did not show hidden
          files in the file chooser.</li>

          <li>the code to check for intersections failed to check
          if there were a crossover in the last tiny section of a
          spline before its end.</li>

          <li>Was generating ofm files when creating bdf fonts.
          Seems unnecessary.</li>

          <li>Was producing a EBLC table with bad first/last values
          for first glyphs.</li>

          <li>Hmm. Not all systems have tzset. Add a configuration
          option for it.</li>

          <li>In scripting, a return within a loop sent ff into an
          infinite loop.</li>

          <li>Kanou's patch for adding a new flag to scripting
          Import, to clear out the layer first.</li>

          <li>Patch from KANOU to add SetGlyphChanged scripting
          function.</li>

          <li>If an implied point became real, this fact was not
          reflected on the display until the user forced a point
          renumbering.</li>

          <li>A mouse click in an empty metrics view references
          garbage memory -- And crashed Kanou's session.</li>

          <li>Loading a large bitmap font left bits of the backmap
          of the encoding map uninitialized.</li>

          <li>Loading a pcf font caused a crash.</li>

          <li>Moving the control points of an implied point should
          move the implied point. And we should indicate which
          points are implied so this behavior doesn't
          surprise.</li>

          <li>Michal Nowakowski points out that renumbering points
          in a glyph should turn off point matching in
          references.</li>

          <li>Add support for bitmaps with vertical metrics.</li>

          <li>Wasn't storing the vendor id in the OS/2 table
          properly.</li>

          <li>Rounding error present on PPC which was absent on *86
          machines.</li>

          <li>Werner would like pixel size info to show on the
          title of a charview when debugging.</li>

          <li>Added a new menu command "Point-&gt;Center Between
          Control Points" for truetype.</li>

          <li>When manipulating menus with keys (rather than mouse)
          Werner found a crash.</li>
        </ul>
      </li>

      <li>5-Dec-2005

        <ul>
          <li>Creating the first bitmap view might cause a crash --
          depending on how the linker organized memory.</li>

          <li>Loading an sfd file now checks to see if there are
          any glyphs with splines in them, and if there are not
          turns on the onlybitmaps flag. Someone pointed out that
          if you inadvertantly edit in the outline view -- even if
          it is nothing significant, then the font is forever after
          marked as outline. This isn't a perfect fix, but it will
          prevent the worst from happening.</li>
        </ul>
      </li>

      <li>1-Dec-2005

        <ul>
          <li>Use GNU gettext rather than my nomen routines to
          handle translation of the UI..</li>

          <li>Add support for plugins.</li>

          <li>I added a check in parsing tfm files to make sure I
          didn't read outside the bounds of the kern table. But the
          table size was expressed in ints (32 bit units), and my
          index was in bytes, so I frequently exceded it.</li>

          <li>If we used Get Info on a reference in a ttf font, and
          that reference did NOT do point matching we would
          generate an inappropriate error.</li>

          <li>My support for using endchar as seac in type2 fonts
          only worked in bare cff fonts, it did not work if the cff
          were inside an sfnt wrapper (opentype).</li>

          <li>I have decided that I will now store all postscript
          strings in utf8 (copyright, weight, familyname, etc.)
          They SHOULD all be ascii. But the occasional copyright
          mark would sneak in. We went into an infinite loop on one
          such because that was an illegal utf8 string. So fix a
          number of problems related to this.</li>

          <li>Switch from using an internal routine to using
          freetype to rasterize b&amp;w bitmaps when debugging ttf
          instructions.</li>

          <li>Make the gridfit/debug settings sticky across
          invocations (store in prefs).</li>

          <li>Add popup info showing the level of greyness in a
          truetype font being debugged in anti-alias mode.</li>

          <li>Werner suggests altering the dynamic range of
          anti-aliased rasters in the charview so that the outlines
          remain visible behind them.</li>

          <li>Make the background color of the debugger raster
          window configurable by the user</li>

          <li>If a curved point had no control point in one
          direction, then ff thought it had no direction and felt
          free to change it. It should inherit the direction from
          the other side of the point. This was even more confusing
          if the point went through a two step process, first
          simplifying one side into a line (losing the cp) then
          simplifying the line away (losing the direction).</li>

          <li>Use a better algorithm to indicate changed pixels.
          (in debug window)</li>

          <li>Screwed up View-&gt;Show Grid Fit... in Mono
          mode.</li>

          <li>Werner wants to be able to see grey scale rasters
          while debugging truetype. He also points out that if the
          instruction before the end of instructions changes
          pixels, ff would leave them marked "changed" even after
          finishing the instructions.</li>

          <li>We were getting multiple error windows.</li>

          <li>Don't allow users to add instructions to a glyph
          containing both a reference and contours. Or a glyph
          where a reference is scaled more than 200%. (tt doesn't
          allow these combinations so the references need to be
          copied inline)</li>

          <li>Typo in remove overlap caused bad bug in feta26.
          Error introduced 15 Sept.</li>

          <li>Further work on what makes a spline linear.</li>

          <li>The utf7 output routine in sfd did not convert from
          utf8 properly.</li>

          <li>Panov has found yet another error in simplify. Be
          really exuberant about turning splines that trace out
          lines into lines.</li>

          <li>Panov finds another bug:

            <ul>
              <li>If we change the unicode value of a glyph, then
              we also need to change</li>

              <li>the unicode value of any references to that
              glyph.</li>
            </ul>
          </li>

          <li>Panov presents four more bugs:

            <ul>
              <li>If an sfd file contains an unencoded glyph, it
              will crash</li>

              <li>Force Encoding-&gt;Original will crash if there's
              a bdf font missing some characters (ie. the piecemeal
              display font)</li>

              <li>Goto Dlg tried to free an uninit value</li>

              <li>Goto Dlg contained a string initialized by latin1
              rather than utf8.</li>
            </ul>
          </li>

          <li>Hmm. the changedsincelasthinted flag doesn't apply to
          truetype. The equivalent thing (I guess) is not having
          any instructions on a glyph with splines.</li>

          <li>Panov wants a way to build up arrays using easier
          syntax than: create array, assign each element.</li>

          <li>Sometimes we would get both an EUC-CN and a
          GB2312packed entry in the Encoding menu.</li>

          <li>Create a plugin for GB12345, and treat it (in sfnt
          tables) as GB2312.</li>

          <li>Add a new scripting funtion: NearlyLines to convert
          almost linear splines to linear.</li>

          <li>Tweak AddExtrema so that it doesn't create Extrema
          points which are too close to the endpoints.</li>

          <li>Didn't terminate an array of answer strings to a
          question dialog.</li>

          <li>Fixed a crash in stem database.</li>
        </ul>
      </li>

      <li>28-Oct-2005

        <ul>
          <li>More work on the mac install procdure.</li>

          <li>Redo the install documentation on the website &amp;
          in the readmes</li>

          <li>Add a hack to the directory browser so that on cygwin
          getting a directory listing of "/" will include the magic
          (fake) directory /cygdrive (which gives access to the
          rest of the PC)</li>

          <li>Add a new scripting funtion: NearlyLines to convert
          almost linear splines to linear.</li>

          <li>Tweak AddExtrema so that it doesn't create Extrema
          points which are too close to the endpoints.</li>

          <li>I was dumping all opentype ligatures into an ofm(tfm)
          file. But I should probably only add 'liga' and 'rlig'
          ligatures.</li>

          <li>Omega has a bug where it thinks 0 width glyphs do not
          exist. Which means it thinks none of the combining
          accents, etc. exist. So force the width of any zero width
          glyphs to be the smallest positive width.</li>

          <li>When reading ttf/otf fonts, FF gave alternate
          substitutions (and multiple subs?) a tag of 0.</li>

          <li>Add two scripting routines to allow people to read
          &amp; write strings from and to files. One string per
          file.</li>

          <li>The ClearTable scripting command parsed the table's
          tag incorrectly.</li>
        </ul>
      </li>

      <li>23-Oct-2005

        <ul>
          <li>Try to make the Mac install a bit more mac-like by
          adding an entry to the X11 Applications menu rather than
          expecting users to start fontforge from the command
          line.</li>

          <li>David Binderman points out an out of bounds array
          reference in cvexport which has been there for years.
          Gleep.</li>

          <li>Add scripting commands for manipulating ttf
          instructions.

            <p>I added the following new scripting functions:</p>

            <ul>
              <li>
              &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;SetMaxpValue("item-name",
              value)</li>

              <li>
              &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;GetMaxpValue("item-name")</li>

              <li>
              &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;ClearInstrs()</li>

              <li>
              &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;ClearTable(tag)</li>

              <li>
              &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;AddInstrs(thingamy,replace,instrs)</li>

              <li>
              &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;FindOrAddCvtIndex(value[,sign-matters])</li>

              <li>
              &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;ReplaceCvtAt(index,value)</li>

              <li>
              &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;GetCvtAt(index)</li>

              <li>
              &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;PrivateToCvt()</li>
            </ul>
          </li>

          <li>Daniel Gillmor points out there is no way to set the
          OS/2 Width field from a script. He then provided a patch
          with two new functions which does this. I realize there
          is no way to set any of the OS/2 values (except panose),
          and there should be (and to retrieve them too).

            <p>I added the following new scripting functions:</p>

            <ul>
              <li>
              &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;SetOS2Value("item-name",
              value)</li>

              <li>
              &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;GetOS2Value("item-name")</li>

              <li>
              &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;SetPrivateValue("item-key","item-value")</li>

              <li>
              &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;GetPrivateValue("item-key")</li>

              <li>
              &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;HasPrivateValue("item-key")</li>

              <li>
              &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;RemovePrivateValue("item-key")</li>
            </ul>
          </li>

          <li>A number of fixes for ofm files.</li>

          <li>When outputting mark-to-base lookups with multiple
          anchor classes, ff would put a base glyph in the coverage
          table several times if it was used by several mark
          classes. Bad.</li>
        </ul>
      </li>

      <li>18-Oct-2005

        <ul>
          <li>KANOU points out that I was using too strict a rule
          for parsing svg polygons.</li>

          <li>OFM output was not working in fonts with lots of
          kerning combinations.</li>
        </ul>
      </li>

      <li>16-Oct-2005

        <ul>
          <li>A number of fixes for ofm files.</li>

          <li>Add default 'nukt' "ligature" substitutions to
          appropriate Devanagari characters</li>
        </ul>
      </li>

      <li>15-Oct-2005

        <ul>
          <li>The patch to the routine determining what glyphs got
          output broke bitmap only fonts.</li>

          <li>Ofm files didn't contain ligatures.</li>

          <li>The ofm patch broke tfm output.</li>
        </ul>
      </li>

      <li>12-Oct-2005

        <ul>
          <li>Add support for generating &amp; parsing ofm files (I
          hope)</li>

          <li>If I tried to generate a font from an absolutely
          empty fontdb (ie. a new one) then I'd get a stupid error
          about how .notdef was at encoding -1 and this was a bad
          idea.</li>

          <li>Add 4 new information types to scripting GlyphInfo

            <dl>
              <dt>* LayerCount</dt>

              <dd>Number of layers in glyph (usually 2)</dd>

              <dt>* RefCount</dt>

              <dd>Number of refs in glyph</dd>

              <dt>* RefNames</dt>

              <dd>Returns an array of all reference names (may be 0
              length)</dd>

              <dt>* RefTransform</dt>

              <dd>Returns an array of all reference transforms</dd>
            </dl>
          </li>

          <li>Don't mark glyphs with widths other than 1em as being
          worth outputting (require widthset). Used to use both
          (because in the early days, before pfaedit moved to
          sourceforge even, the widthset bit didn't exist). Now
          there are too many cases w here glyphs are created with a
          width other than 1em (marks, glyphs in monospace fonts
          (where the space is anything but 1em)).</li>

          <li>When printing a type3 pdf font, give it a name. Not
          required, but so what.</li>

          <li>Patch from Michal Nowakowski. When editing truetype
          instructions using my prefix notation for numbers, there
          was a crash if a number needed a word (rather than a
          byte).</li>

          <li>Add some support for reading fonts out of a pdf file.

            <ul>
              <li>Limited support for pdf type3 (no images)</li>

              <li>Only support (Hex, 85, Flate, RLE)Decode filters
              (no support for lzw, fax, JBIG, DCT)</li>
            </ul>
          </li>

          <li>The routine to build the stem database (autohint)
          would set up a point database and then call a routine to
          convert all splines into a set of monotonics. But that
          routine could remove 0 length splines (and the points
          attached), which would mean our point db would be
          wrong.</li>

          <li>Stefan Wanger suggests some patches to fix memory
          leaks.</li>

          <li>Stefan Wanger gave me a type2 font which used type1
          flex conventions (calling othersubrs, etc.) There is no
          othersubrs operator in type2, nor any place to store
          othersubrs subroutines. But it is easy enough to support,
          so why not. Warn that it's an illegal font, of
          course.</li>

          <li>Stefan Wanger gave me a font containing the utf8 byte
          order mark in a fontname ( in a CFF Name Index).
          PostScript says FontNames are printable ASCII. But it's
          easy enough to skip over it.</li>

          <li>Stepan Roh points out that in a monospace font,
          combining glyphs should default to the mono-width while
          in a proportional font they should default to 0 width (or
          perhaps 1 em-unit for compatability with old idiotic
          windows systems). Use the panose field to determine if a
          font is monospace.

            <p>Actually ALL glyphs in a monospace font should
            default to the mono-space width rather than 1em.</p>
          </li>

          <li>New dialog: Hints-&gt;Edit 'maxp'... Gives user
          access to number of functions defined, the stack depth,
          storage usage, number of twilight points, which ff can't
          figure out for you.</li>

          <li>Figured out how to make transparent images work on
          cygwin</li>

          <li>Michal Nowakowski points out that negative values are
          duplicated in cvt.</li>

          <li>Patch from Michal Nowakowski fixing crash when
          setting size of cvt table to 0.</li>
        </ul>
      </li>

      <li>29-Sept-2005

        <ul>
          <li>Add utf8 entry points for many (ucs2) routines.
          Minimal ability to draw non-BMP glyphs now with <a href=
          "nonBMP/index.html">bdf fonts</a> with encodings:
          *-UnicodePlane-1 (for plane 1), *-UnicodePlane-2 (for
          plane 2), etc.</li>

          <li>Add a menu command to add values from the private
          dict into the cvt table (BlueValues, StemSnaps).</li>

          <li>The Edit cvt window usually failed to draw anything
          in itself when it popped up (subsequent refreshes were
          ok).</li>

          <li>Patch from Michal Nowakowski to improve memory usage
          in auto instr.</li>

          <li>Printing sample text was broken in fonts with no
          kerning classes.</li>

          <li>cygwin does very weird things with shared libaries,
          and we didn't support them at all.</li>

          <li>FontForge did not support the deprecated usage of
          endchar to mean (almost) seac in type2 charstrings. It
          should now.</li>

          <li>os2 typo linegap was not read out of sfd files.</li>

          <li>Display 'gai' files in the open dlg.</li>

          <li>I got some mnemonics wrong. Fix 'em up.</li>

          <li>bdftopcf will use the glyph encoded at 0 as the
          default glyph if there is no explicit DEFAULT_CHAR. It
          seems happy with a DEFAULT_CHAR of -1 to mean no default,
          so use that if we don't want glyph 0 to be the
          default.</li>

          <li>when outputting bdf, fnt or pt3 bitmap fonts with no
          outline font generated, we'd get filenames like
          foo-*-13.bdf. Get rid of the "-*".</li>

          <li>Support point numbering of composites even when not
          debugging.</li>

          <li>Michal Nowakowski points out that the cvt editor
          crashed if we changed the length of the table.</li>

          <li>Provide two new scripting functions:

            <ul>
              <li>
              MoveReference(xoff,yoff,[ref-name/ref-unicode]+)</li>

              <li>
              PositionReference(x,y,[ref-name/ref-unicode]+)</li>
            </ul>

            <p>These search all selected glyphs, looking for any
            references in those glyphs with the given name/unicode
            value, and then translating the reference by
            (xoff,yoff) or positioning the reference absolutely at
            (x,y).</p>
          </li>

          <li>ff failed to read horizontal metrics properly from a
          type2 CFF CID font. In most cases this would be masked by
          the fact that ff would correct the bad width values by
          reading the hmtx table. But if one had a bare CFF font,
          or a 'gai' font where there is no external source of
          widths, ff would get things wrong.</li>

          <li>Alexej Kryukov points out that most entries in the
          private dict should be scaled when we do a
          ScaleToEm.</li>

          <li>Fix a couple of problems with cid font display that
          "gai" fonts expose.</li>

          <li>Michal Nowakowski points out that I generated
          truetype instructions --- and then forgot to attach them
          to the glyph. Whoops.</li>

          <li>Loading extensible glyph information from a tfm file
          was broken by the encoding change.</li>
        </ul>
      </li>

      <li>19-Sept-2005

        <ul>
          <li>ff did not read AAT classes (kerning classes, etc)
          properly. It read one extra element which could cause
          problems</li>

          <li>Cleanup svg output for kerning classes with no
          members.</li>

          <li>Out of bounds array reference in OS2FigureCodePages
          caused a crash on the mac.</li>

          <li>When loading a type1 font we failed to set the
          unicode encoding on seac references. This probably broke
          lots of things, it certainly broke replace with
          reference.</li>

          <li>Add a DefaultRoundToGrid scripting function to set
          the Round-to-Grid truetype reference bit (basically set
          it whenever we have a reference which isn't point
          matched).</li>

          <li>Add support for truetype point matching in references
          and anchor points</li>

          <li>Improve the debugging heuristic that notices when
          we've jumpped to a new routine to work better with
          composites</li>

          <li>If I attempted to debug a glyph with no instructions
          there was a race condition and if the race was won one
          way, ff would hang.</li>

          <li>We weren't numbering points in a composite. This was
          only obvious when we did a View-&gt;Show Grid Fit on a
          composite glyph.</li>

          <li>When debugging a composite glyph, ff forgot that some
          references are translated (or scaled or rotated), and
          failed to display this.</li>

          <li>FF failed to keep track of the truetype "RoundToGrid"
          bit which applies to references.</li>

          <li>In the Points window of truetype debugging, if the
          penultimate point of a contour was interpolated, then the
          contour boundary was drawn in the wrong place.</li>

          <li>Use to store debugging dpi/pointsize in the charview.
          Werner suggests that it be global (so different glyphs
          will all share the same defaults).</li>

          <li>Some Unicode code blocks have moved (probably those
          which only in the pipeline or some such), and some others
          have been added to the pipeline.</li>
        </ul>
      </li>

      <li>15-Sept-2005

        <ul>
          <li>Can't use a subroutine to refer to a translated glyph
          which contains flex hints in type1 output.</li>

          <li>Hide another problem with rounding errors in remove
          overlap.</li>

          <li>Don't produce multiple warnings about the local
          encoding.</li>

          <li>In quadratic fonts the Remove Overlap menu item is
          disabled, but if you use the hotkey the command is
          invoked (with disasterous results).</li>

          <li>Typo in point info code to determine whether a hint
          mask contains conflicts (matched vertical hints against
          horizontal ones)</li>
        </ul>
      </li>

      <li>12-Sept-2005

        <ul>
          <li>Added a scripting command DefaultUseMyMetrics() to
          set the use_my_metrics bit in old fonts.</li>
        </ul>
      </li>

      <li>11-Sept-2005

        <ul>
          <li>&nbsp;&nbsp; When ff pastes refs from one font to
          another it tries to figure out the width of a glyph
          containing references from the width of what appears to
          be the base glyph. (because if you paste Aacute from one
          font to another, the size of the "A" glyph may be quite
          different in the new font. Using the width of the glyph
          in the original font would be wrong).

            <p>There are two problems with this:</p>

            <ol>
              <li>It didn't take forward references into account,
              and would use the original width rather than the
              modified width of the reference.</li>

              <li>It would (probably) be confused by an Alphatonos
              where the width of Alphatonos is not the same as that
              of Alpha.</li>
            </ol>

            <p>instead figure widths out after all pastes have
            completed, looking at the use_my_metrics bit to get
            things right.</p>
          </li>

          <li>Handle forward references to glyphs which will be
          pasted into by the current command (used to work, broken
          by the encoding change)</li>

          <li>Various fixes for pasting references from a font
          which has since been closed.</li>

          <li>Support the ttf "_USE_MY_METRICS" bit on composite
          glyphs. This entails:

            <ul>
              <li>Retaining it when reading a truetype font</li>

              <li>Setting properly when generating one</li>

              <li>Storing it in sfd files</li>

              <li>Giving the user a way to set it with the
              Element-&gt;GetInfo command</li>
            </ul>
          </li>
        </ul>
      </li>

      <li>9-Sept-2005

        <ul>
          <li>ff crashed when given a bdf font with multiple glyphs
          with the same name</li>

          <li>Try to avoid generating bdf fonts with multiple
          glyphs with the same name. This happened when a single
          glyph was mapped to several encodings, a concept bdf
          doesn't support. Now when it looks like this will happen
          we rename the glyph.</li>

          <li>Uninitialized variable in dependant sub-menu (broken
          by encoding change)</li>

          <li>Pasting a reference into a font which did not contain
          the referred glyph did not give you the option of copying
          the original outlines any more. (broken by the encoding
          change)</li>

          <li>Merging fonts where glyphs had multiple encodings
          caused crashes.</li>

          <li>I'm very old fashioned. I like having error messages
          on stderr. But far too many people don't see them there.
          I guess they invoke fontforge directly from X with stderr
          directed to some invisible console window. Well create a
          little window to contain warning messages about font
          errors (for instance when reading an otf font we might
          complain about glyphs out of bounds, etc.)</li>

          <li>Add support for postscript bitmap fonts. This means:

            <ul>
              <li>Ability to parse (simple forms of) the imagemask
              ps operator</li>

              <li>Code to detect that a type3 is a ps bitmap, and
              convert it into a normal bitmap font that people can
              edit.</li>

              <li>Bitmap output as a ps type3 font (using
              imagemask)</li>

              <li>Fixing a bug in my output routines which worked
              fine for images in eps files, but failed horribly if
              that same code was stuffed into a charproc and
              executed on demand.</li>
            </ul>
          </li>

          <li>ff could not handle an encoding specified as a simple
          array. (Not allowed in typ e1 spec, but obvious for a
          type3)</li>

          <li>And ff's handling of any type3s was broken by the
          encoding patch.</li>

          <li>If a font contained fewer than 256 glyphs, then ff
          failed to load a format0 cmap subtable properly.</li>
        </ul>
      </li>

      <li>4-Sept-2005

        <ul>
          <li>In fontinfo, changed the tab "TTF Values" to be
          "OS/2", consolidated the Panose tab underneath it. Added
          many more fields, almost all of OS/2.</li>

          <li>Fixed a number of uninitialized variables, at the
          instigation of Pavel Roskin.</li>

          <li>Applied several patches from Pavel Roskin.</li>

          <li>The scripting WorthOutputting command insisted on an
          argument, even when it should not have.</li>

          <li>Scripting SetCharCnt command has been broken since
          the encoding change.</li>
        </ul>
      </li>

      <li>31-August-2005

        <ul>
          <li>The mac fix for 25-Aug wasn't quite enough.</li>

          <li>I used to maintain a hidden value of the os2 linegap.
          This didn't change when users set linegap with font info,
          leaving users annoyed.</li>

          <li>It used to be that both the Hint-&gt;Add Hint and
          Hint-&gt;Create Hint commands would destroy all hint
          masks. Now we update those hint masks appropriately.</li>

          <li>The "Original" encoding was broken, and reencoding to
          it gaves us 256 blank glyphs before glyph0. Sigh.</li>

          <li>The CodeRange bit for symbol doesn't mean the font
          contains any standard set of "symbol" glyphs, but rather
          either that it has a 3,0 cmap sub-table, or that there
          are glyphs mapped to 0xf000-0xf0ff in the 3,1 (unicode)
          sub-table.

            <p>Setting this bit should give you a symbol encoding
            as well as all the other encodings you've set bits for.
            It doesn't work under windows. It doesn't work.
            TrueType fonts do not provide a symbol encoding, while
            'CFF ' fonts only provide a symbol encoding. But hey,
            let's support it anyway!</p>

            <p>change View-&gt;Goto to know about this range as MS
            Symbol.</p>
          </li>

          <li>Importing an eps file (or pasting the x clipboard)
          made use of an uninitialized variable. (introduced
          7-Aug)</li>

          <li>Cleanup pasting references from one font to another
          (gave some very strange results when pasting refs with no
          unicode encodings).</li>
        </ul>
      </li>

      <li>25-August-2005

        <ul>
          <li>Recode the mac resource fork routines so that they no
          longer use the FSSpec structure. 10.4 complains about
          it.</li>

          <li>Bug in mm font charstring generation.</li>

          <li>If a font contained mac feature setting names, then
          when ff generated it, ff would produce duplicate entries
          in the 'name' table for these guys. One for the name in
          the font itself, and one for the name ff thought that
          feature setting should have.</li>

          <li>Nobody else puts apple unicode names into the 'name'
          table so I probably should not either. Adobe says one
          should not. Apple's website implies one should -- but
          Apple doesn't and its ttf website is not very
          accurate.</li>

          <li>When ff generated a ttf/otf font with applemode set
          and opentype off then the font would have version 'true'.
          Which means windows would reject it. That's probably not
          a good idea given that this situation is default on the
          mac -- even if we don't have a GSUB/GPOS table we should
          at least let the glyphs show on windows.

            <p>On the other hand some people might want to make
            fonts that only work on macs. So add a configure
            flag.</p>
          </li>

          <li>ff couldn't undo changing the lig carets (if it
          weren't compiled for multilayer)</li>

          <li>Copying a pairwise positioning left memory in a bad
          state.</li>

          <li>Coalesce all lookups with the same feature &amp;
          script lang. This makes ATM happy about kerning on
          windows.</li>

          <li>When rasterizing a multilayer font we would sometimes
          get warnings from the stroker about how the stroke
          self-intersected. Get rid of those warnings.</li>

          <li>Pasting from a multilayered font into a normal one
          crashed</li>

          <li>If an order2 font were turned into a PS font, then
          characters with hint conflicts got no hints.</li>

          <li>Makers of fonts on the mac often use out of bound
          GIDs as flags in contextual su bstitutions. What I have
          seen is that one sub-table will insert such a "glyph" w
          hen a match is found, and then the next sub table will
          remove the flag, and perf orm subsequent transformations.
          This is important on the mac because there is a limited
          number of substitutions that can happen once a match is
          found, but if a match is found at the start (ie. the
          match being some magic marker glyph) then u nlimited
          substitutions are available. When ff first stumbled on
          these fonts it crashed, then it treated a gid&gt;glyph_cn
          t as an error (and so it ignored the substitution). I've
          just put in code that c reates dummy glyphs for all these
          bizarre GIDs so (I hope) the font will work af ter
          passing through ff (only there will be some real blank
          glyphs at the end of the font rather than vaper-ware
          glyphs).</li>

          <li>The Active Hints pane (of Point Info) didn't always
          work if a glyph had more than one contour.</li>

          <li>Be more canny in the use of subroutines for
          references in type1/2 output.</li>

          <li>When generating contextual lookups, ff did not set
          the lookup count between gpos and gsub. So if a font had
          both contextual gpos &amp; gsub elements ff got
          confused.</li>

          <li>The code for cff encodings (ie. in bare cff non-cid
          fonts) didn't handle multiply encoded glyphs</li>

          <li>Change the default color of the prev control point
          (so it's easier for me to see)</li>
        </ul>
      </li>

      <li>11-August-2005

        <ul>
          <li>The configure script did not find libfreetype when it
          lived (solely) in /usr/X11R6/libs</li>

          <li>On the Mac, menus incorrectly suggested using Cmd
          rather than Ctl. (Cmd used to work on earlier versions of
          the X server, but now it is snagged by the X11 menubar
          itself.)</li>

          <li>ff uses the Alt/Meta key to alter the behavior of
          some tools (magnify, ruler, pointer, pencil, etc.) in the
          editing windows. This doesn't work well on the mac. First
          there is no real Alt/Meta key. If we contemplate using
          Option or Command it will generally already be used to
          turn the single button mouse into a three button mouse
          (Option - mouse =&gt; button 2, Command - mouse =&gt;
          button 3). So instead use the CapsLock key.</li>
        </ul>
      </li>

      <li>9-August-2005

        <ul>
          <li>The big5 encoding stopped at 64000, which confused
          routines which expected unencoded glyphs to start at
          65536.</li>

          <li>We would crash when reencoding a font with enough
          unencoded alternate unicode code points.</li>

          <li>The code for creating an 8/16 cmap subtable didn't
          work.</li>

          <li>ff would crash if it had two windows open on the same
          font and one got reencoded</li>

          <li>Didn't set the length of the format4 'cmap'
          sub-table, so the offset to the format12 (32bit unicode)
          table was wrong.</li>

          <li>ttfcopyfile can complain about a ttf table offset
          being wrong. Give it the info so that it will now tell us
          which table has the wrong offset.</li>

          <li>Uninitialized variable in metricsview when creating a
          popup window.</li>

          <li>Redo the ttfnames pane of the font info dlg. Now show
          the names as an editable list.</li>

          <li>Histogram dlg still used wrong encodings for selected
          glyphs when historgrams invoked from Hints menu.</li>
        </ul>
      </li>

      <li>7-August-2005

        <ul>
          <li>SelectIf failed when passed an encoding which was out
          of bounds</li>

          <li>Added a new scripting command: ToString</li>

          <li>Using the X clipboard to paste a glyph into a glyph
          that contained stuff caused a crash.</li>

          <li>Using the X clipboard to paste a glyph with
          references or with multilayer did no t work.</li>

          <li>None of ttf, otf nor svg got multiply encoded glyphs
          output properly.</li>

          <li>FF screwed up memory when creating ligatures from an
          svg font.</li>

          <li>Merge fonts was writing to bad memory.</li>

          <li>FF was confused by a strange MM font</li>

          <li>FindExistingSlot should understand altuni.</li>

          <li>Font View didn't display current unicode of multiply
          encoded glyphs. (same for popups).</li>

          <li>Still having problems generating type1 code for
          complicated reference glyphs.</li>

          <li>Retain knowlege of multiple unicode encodings for
          some glyphs. Used when a glyph has multiple encodings and
          is reencoded.</li>

          <li>Add back an option to compact an encoding. It's not
          the same as the old compact which kept track of the
          former encoding. This just compacts, user must explicitly
          reencode.</li>

          <li>Force encoding didn't work if the new encoding had
          more slots than the old.</li>

          <li>FF also failed to parse glyph based contextual
          lookups properly</li>
        </ul>
      </li>

      <li>3-August-2005

        <ul>
          <li>FF failed to parse class based contextual lookups
          properly (contextual chaining lookups were ok)</li>
        </ul>
      </li>

      <li>2-August-2005

        <ul>
          <li><span class="c2"><strong><big>The OS/2 ulCodeRanges
          field has been broken for a long time, and has failed to
          mark the presence of any latin code
          pages.</big></strong></span></li>

          <li>The ulCodeRanges field never set Vietnamese,
          TradChinese, Mac nor PC OEM</li>

          <li>FF did not support EUC-CN, ISO-2022-CN, ISO=2022-KR
          iconv encodings properly.</li>

          <li>Work around a bug in iconv's support for CP1258</li>

          <li>Put some code in to warn users about unknown
          language/locales in the ttf 'name' table.</li>

          <li>Enter some new language/locale codes for ms.</li>

          <li>Crash when moving the end of an open path in an
          order2 font.</li>

          <li>If one loaded an encoding specified by codepoint and
          then cancelled the dlg which asked for a name for that
          encoding, then ff would crash.</li>

          <li>Don't use Adobe's glyphnames when they are obviously
          wrong (use uni???? instead)</li>

          <li>Add (better) support for the new dotlessj</li>

          <li>Put a check into the context chain dlg to make sure
          that people don't add sequence/lookup pairs where the
          sequence number is too big.</li>

          <li>Make class be the default format for
          contextual/chaining substitutions rather than coverage
          tables.</li>

          <li><span class="c2"><strong><big>The format of the
          LineBreak.txt file changed with Unicode 4.1, so all the
          line break info is wrong (essentially lines never broke
          in text fields).</big></strong></span></li>

          <li>Reference to bad memory when creating a popup in
          combinations list.</li>

          <li>Still problems in the 'name' table when Mac &amp; Mac
          Unicode strings don't match.</li>

          <li>Use of the X clipboard for transfering glyphs
          resulted in a crash</li>

          <li>When generating an old-style 'kern' table (either
          OpenType nor Apple modes set) decompose all kerning
          classes into kern pairs as we do for AFM files.</li>

          <li>Scripting didn't have a way to generate a font with
          neither Apple nor OpenType tables. Add one.</li>

          <li>Oops. wrong default extension for otb fonts from
          scripts.</li>

          <li>Fix some potential crashes where loading font types
          left a new field unset.</li>
        </ul>
      </li>

      <li>28-July-2005

        <ul>
          <li><span class="c2"><strong><big>Redesigned the way
          encodings are handled. From the user's perspective
          Encodings are no longer controlled by FontInfo, but via
          an encoding menu.</big></strong></span></li>

          <li>If we create a bitmap strike in an empty font then
          change the fontview to look at the strike.</li>

          <li>The SetWidth command of FontView produced garbage
          defaults for empty fonts</li>

          <li>Don't set the hinting needed bit on: bitmap only
          fonts, multilayered fonts, stroked fonts nor quadratic
          fonts.</li>

          <li>Fix some problems with the generated names in
          File-&gt;Generate multiple</li>

          <li>The Save command failed to reset the font window's
          title (so it still looked modified)</li>

          <li>The enabled state of Encoding-&gt;Detach Glyphs was
          wrong</li>

          <li>FF still didn't allow two ligatures to be created for
          the same glyph (ie. it complained if you tried to make
          both "f + f + i =&gt; ffi" and "ff + i =&gt; ffi"</li>

          <li>Added a TypeOf command to scripting</li>

          <li>Added a GetPosSub command to scripting.</li>

          <li>Werner says negative widths and depths be set to 0 in
          tfm files.</li>

          <li>FontForge was generating an incorrect warning
          message. If a 'name' table contains a duplicate entry for
          a given platform/specific/language/id that's an error in
          the font. But ff conflated mac names with window names
          and so was only checking language/id. So if the mac
          windows names were different (which is probably a bad
          design idea, but not an error) ff said it was wrong. It
          can also be caused by using a character in the string
          which is not in the Mac Encoding for that language.</li>

          <li>Don't set "Hinting needed" flag in bitmap only
          fonts.</li>

          <li>AutoHint had a crash if there were open contours in a
          glyph being hinted.</li>

          <li>Add a couple of browsers to the list to check by
          default.</li>

          <li>Using the kerning pair closeup dlg to create a new
          kerning pair caused a crash (eventually).</li>

          <li>When saving a block of ttf bitmap glyphs all with
          about the same metrics,</li>

          <li>Kern pairs were not scaled to emsize when loading
          from an afm file.</li>

          <li>Add a series of new selection commands, to the font
          view and to scripting:

            <ul>
              <li>SelectChangedGlyphs</li>

              <li>SelectHintingNeeded</li>
            </ul>

            <p>(just to scripting)</p>

            <ul>
              <li>SelectSingletons</li>

              <li>SelectMoreSingletons</li>

              <li>SelectFewerSingletons</li>
            </ul>
          </li>

          <li>Revert Glyph didn't work. One bug caused by
          multilayer, one caused by encoding changes, and one
          really old one.</li>

          <li>GetFontNames returned an uninitialized value on bad
          ttf files.</li>

          <li>Add some new scripting commands to access the TeX
          per-glyph fields.</li>

          <li>Werner suggested some improvements to tfm
          output.</li>

          <li>Cleanup behavior of generating ttf bitmaps in a
          script.</li>

          <li>I was attaching script/langs to lookups when parsing
          GPOS/GSUB. That wasn't good enough. Each sub-table and
          have it's own set, so attach script/langs to subtables as
          well. Still a flaw in that sub-tables could be referenced
          through severel extension sub-tables or directly and I
          don't unravel that complexity until too late.</li>

          <li>ATM which handles some kerning for otf fonts for
          Word, does not handle 'kern' features where the feature
          contains more than one lookup. So whenever we have a
          feature with multiple lookups try to compress them into
          one lookup with multiple sub-tables.</li>

          <li>Transform (in fontview) and Scale To Em do not scale
          the vertical advance.</li>

          <li>We didn't test the right thing when deciding where a
          subroutine containing refs began.</li>

          <li>Remove Undoes was broken by the encoding
          changes.</li>

          <li>When saving multiple, make sure we don't get
          extraneous kerns. (to glyphs not in the current
          sub-font).</li>

          <li>Make sure the blue lines (marking hints needing to be
          updated) get cleared properly.</li>

          <li>Some display problems in the SameGlyphAs
          command.</li>

          <li>The Apply Substitutions code did not consider the
          possibility of loops:<br />
          a-&gt;b-&gt;c-&gt;d-&gt;a</li>

          <li>Werner suggests indicating multi-layer in the version
          string.</li>

          <li>Mark to Mark anchor classes should allow each mark
          glyph also to contain a base mark entry.</li>

          <li>Give unicode name data (in grey) for dotted names.
          (ie for A.super give unicode name data for "A", but in
          grey so it stands out as modified).</li>

          <li>Add scripting routines to detach glyphs from the
          encoding and to remove them from the font.</li>

          <li>FF produced some very strange 'gasp' tables...
          depending on the bitmap fonts in the sfd and not on the
          bitmaps in the output ttf for one thing.</li>

          <li>Werner wants an Invert Selection command.</li>

          <li>The position of Coptic and Glagolithic has been
          shifted in Unicode 4.1 (shifted from some earlier
          proposal).</li>

          <li>Patch by KANOU, ttc files were broken.</li>

          <li>Some english language strings in the ttfnames pane of
          fontinfo where sort of bound to equivalent fields in the
          names pane. Make this clearer, and consistent.</li>

          <li>Werner thinks my error messages for scripts should be
          improved.</li>

          <li>Add a check in case sfd files contain unreasonable
          values for pixelsize, etc.</li>

          <li>Werner suggests a --dry &lt;scriptfile&gt; argument
          which does syntax checking without actually executing the
          script. I think it is trivial.</li>

          <li>Werner points out that the DSC Version comment has a
          very specific syntax:<br />
          %%Version: &lt;version&gt; &lt;revision&gt;<br />
          &lt;version&gt; is a real, &lt;revision&gt; is a uint. So
          we can't use the font's version string here (which might
          be anything). Instead we now generate a version
          comment<br />
          %Version: &lt;string&gt;<br />
          rather than a DSC Comment.</li>

          <li>We used to assign a unicode value to ".notdef"s when
          reading ps encoding file, if the encoding was in the
          region of control chars (so location 1 would get uni0001,
          while location 65 would get -1). Seems inconsistent.</li>

          <li>Oops. I failed to provide a mechanism to add other
          iconv encoding names into my menu.</li>

          <li>Code to support group display.</li>

          <li>Was not reading ps encoding files properly.</li>

          <li>Remove encoding should always be available.</li>
        </ul>
      </li>

      <li>19-July-2005

        <ul>
          <li>Extend to Unicode 4.1</li>

          <li>Change to configuration system to allow relative
          pathspecs for --with-freetype-src didn't work.</li>

          <li>Context chain dlg had problems with empty patterns
          (no terminal NUL in empty string used to represent
          them)</li>

          <li>The [EditData] button in contextual fontinfo pane was
          disabled due to reasons which are no longer valid..</li>

          <li>Transforming by a negative scale factor screwed up
          the hints.</li>

          <li>Add move up/down buttons to the kerning class dlg
          (class lists area) Use the selection from the class lists
          to highlight offsets.</li>

          <li>Print sample did not handle kerning by classes.</li>

          <li>When we had: a glyph which contained refs where that
          glyph was itself used as a reference in another glyph and
          all glyphs (except the last) lived in subroutines then we
          got multiple declarations of hints and the middle glyph
          was translated from where it should have been.</li>

          <li>When changing lists they should not scroll back to
          the beginning.</li>

          <li>Various fixes regarding hints: changing hints should
          set the char changed flag changing a glyph should mark
          all glyphs that refer to it as having out of date hints
          display out of date hints in font view. hints weren't
          being preserved (and should have been) in charview in
          Paste and transform.</li>

          <li>Apply Substitutions was badly broken when ff compiled
          with multilayer.</li>

          <li>Kern Pair dlg looked at garbage memory when it closed
          (and crashed sometimes).</li>

          <li>ff decides whether to add a 'gasp' table to a font
          based on whether the font has instructions or not. ff's
          own ttf fonts contain instructions in .notdef but nowhere
          else, so ignore .notdef when making this check.</li>

          <li>One more attempt to rule out absurd results in
          simplify().</li>

          <li>if the lsb/rsb dlg was given a negative value it
          complained about negative widths. (whether the width
          would have been negative or not).</li>

          <li>$italicangle has been broken since I added reals to
          scripting.</li>

          <li>The kernclass dialog did not handle deleted classes
          properly.</li>

          <li>Add ability to undo hints.</li>

          <li>Once again starting a browser on windows is
          broken.</li>

          <li>We didn't do a bounds check when indexing into the
          names array of an encoding (when building a character
          from scratch). If the index was huge the result was
          garbage, generally leading to a crash sometime
          thereafter.</li>

          <li>An open path consisting of a single point caused
          replace with reference to crash.</li>

          <li>Generating a postscript resource font on the mac from
          a script did not work.</li>

          <li>Werner points out that afm files generated by
          FontForge still claim to have been made by pfaedit.
          Oops.</li>

          <li>Didn't parse user defined encodings properly and
          often omitted the first glyph.</li>
        </ul>
      </li>

      <li>24-June-2005

        <ul>
          <li>Improvements in the way type42 fonts where handled in
          printing.</li>

          <li>Fix a crash when parsing mangled cff files</li>

          <li>Marvelous triple bug:

            <ul>
              <li>Adobe's Tech Note 5176 (cff format) says that a
              private dict is required. They mean it's required in
              a type1 font.</li>

              <li>Because of this I put a null private dict entry
              into my cid cff fonts.</li>

              <li>ghostview finds the null private dict entry and
              tries to read data from it even though it is of 0
              length.</li>
            </ul>
          </li>

          <li>Add postscript code necessary for loading a cff font
          to my cff font output.</li>

          <li>Fix some uninitialized variables in the display
          dlg.</li>

          <li>We didn't get DSC pages properly when printing a CID
          keyed font.</li>

          <li>The default (notdef) glyph generated by my palm
          output routines was a little wonky.</li>

          <li>The rle image reader in my sfd routines had an off by
          one error causing it to reject some images.</li>

          <li>We used to munch memory when loading empty glyphs
          from mac NFNT resources.</li>

          <li>It used to be that we didn't set the default
          background until the first font view window was opened.
          This meant that if we loaded a grey scale bitmap before
          opening a window (ie. from the command line) then that
          bitmap's clut would be relative to white rather than the
          appropriate background.</li>

          <li>Add some code to protect against badly generated
          bitmap strikes in sfnts.</li>

          <li>vhea &amp; vmtx tables were generally wrong in otf
          fonts (unless the last full vmetric happened to be the
          last full hmetric). Also fix problems with cid hmtx
          output.</li>

          <li>The sfd reader looked in the wrong place for sli
          information in cid keyed fonts.</li>

          <li>Damn. Default output (for stdout) encoding never gets
          initialized when in a script.</li>

          <li>I realized a few months ago that there is a
          difference between encodings based on names and encoding
          based on unicode codepoints. Unfortunately I was only
          saving encodings as though they were based on names
          (generating default names if necessary). This patch
          retains the distinction even when encodings are saved to
          the preferences folder.</li>

          <li>AddAccent behaved differently when passed a glyphname
          and a unicode code point. In the first case it used the
          glyph specified. In the second it performed an arcane
          search which would not always use the specified glyph
          (left over from the days when it was important to use a
          glyph in Adobe Standard so you could do a seac).</li>

          <li>When debugging composite glyphs ff failed to notice
          when we switched from one glyph to another and so failed
          to reset the instruction list to those of the new
          glyph.</li>

          <li>Problem with cubic to quadratic spline approximation.
          Fixed by a more careful comparison between original and
          resulting spline.</li>

          <li>Kerning (and Anchor positioning) didn't work when
          printing to pdf.</li>

          <li>Won-kyu Park points out that ff's internal utf7
          parser (deep in the guts of sfd.c) only parses utf7
          strings as produced by ff. He took a utf7 string produced
          by python and inserted it and ff could not read it. He
          provides a patch to fix the problem.</li>

          <li>If we got an invalid second order spline, let's fix
          it up into some vaguely reasonable form, so the poor user
          doesn't keep getting errors.</li>

          <li>Extra "-" in type42 header removed.</li>

          <li>The anchor dialog was all screwed up.</li>

          <li>The test in show att that all components of a
          substitution existed failed to handle a trailing
          space.</li>

          <li>Make page Up/Down work in Show ATT</li>

          <li>Sometimes the simplify algorithem fails to
          converge.</li>

          <li>When generating a tfm file the width (height, depth,
          ic) table was being scaled twice.</li>

          <li>Remove a NaN that occurred when moving quadratic
          splines.</li>

          <li>Oops. The unicode code point of a glyph was
          restricted to BMP by Glyph Info dlg.</li>

          <li>Werner gave me a font where the glyphs were not
          properly ordered. So you can't tell the length of a glyph
          by loca[i+1]-loca[i]. The data appear valid in spite of
          that. So put in a warning for this particular case (we
          were generating a warning, but it wasn't as meaningful as
          it might be.)</li>

          <li>Make View-&gt;Show ATT aware of the mark attachment
          class info so it can show the classes.</li>

          <li>When interpolating to quadratic fonts where the two
          designs didn't match then the various possible errors
          gave us bad splines: Different numbers of points on the
          paths meant that the control points at the end (after we
          reached the end of the contour in one design but not the
          other) didn't match. Different designs meant that
          interpolating a line (with no control points) to a curved
          spline again produced nasties.</li>

          <li>Drag and drop was broken.</li>

          <li>Extend lookup flags support to include mark
          attachment classes (as defined in GDEF).</li>

          <li>Bad argument type checking on the AddAccent scripting
          command.</li>

          <li>Infinite loop in a rare case involving a flex hint at
          the start of a contour.</li>

          <li>The merge fonts command would crash.</li>

          <li>Problems parsing some bare cff fonts.</li>
        </ul>
      </li>

      <li>2-May-2005

        <ul>
          <li>Add support for Mark Classes.

            <ul>
              <li>New pane in Font Info to create them</li>

              <li>New field in the feature tag dlg to use them</li>

              <li>Input/Output routines</li>
            </ul>
          </li>

          <li>Drag and drop was broken</li>

          <li>Infinite loop in some bizarre cases when generating a
          hinted opentype font.</li>

          <li>The Merge Fonts command was broken</li>

          <li>The scripting command: AddAccent checked for the
          wrong argument type</li>

          <li>ff generated an error when loading some bare cff
          fonts.</li>

          <li>Store desired fontview sizes in prefs file</li>

          <li>Add a tweak to make the mac's dynamic loader look for
          fink libraries</li>

          <li>Problems parsing bare cff cid-keyed fonts</li>

          <li>recognize that code page 932 is a variant of
          SJIS</li>

          <li>The feature tag 'nutf' is an obsolete name for
          'afrc'</li>

          <li>Add a couple of new scripting functions

            <ul>
              <li>Int() which casts its real/int/unicode argument
              to int</li>

              <li>UCodePoint() which casts its real/int/unicode
              argument to unicode</li>
            </ul>
          </li>

          <li>scripting CharInfo no longer creates the glyph it is
          asked about</li>

          <li>WorthOutputting/DrawsSomething can now be applied to
          the current selection</li>

          <li>When using the freetype rasterizer don't do an
          automatic close of open paths.</li>

          <li>For SCWorthOutputting I used to check both that
          !widthset and width==em-size. Remove the em-size check,
          should be redundant and somethimes (marks) is wrong.</li>

          <li>The various FindBounds routines didn't pad stroked
          fonts appropriately</li>

          <li>Discrepency in docs and code on spelling of scripting
          Auto[tT]race command. Accept both variants</li>

          <li>A debug statement was left in the ps interpreter</li>

          <li>Make the help command look for japanese docs in the
          ja locale</li>

          <li>Add a select fewer scripting command</li>

          <li>Fix some problems with custom encodings</li>

          <li>Support '\r' and '\r\n' as line-endings for backslash
          continuation</li>

          <li>New version of Japanese UI</li>

          <li>The kerning pair dlg would sometimes fail to display
          a pair when searching on the second char of the
          pair.</li>

          <li>Danish translation of some style names, courtesy of
          Anders Lund</li>

          <li>Fix some problems with SJIS encoding</li>

          <li>The point info dlg was quite unusable if you typed in
          somethng which wasn't a number</li>

          <li>When in debug mode display pointer position in
          pixels</li>

          <li>Point Info had problems with order2 splines</li>

          <li>The instruction pane of the debug window was
          interpretting keystrokes it should not have</li>

          <li>Peter Selinger has changed the way potrace is built
          so it no longer uses cygwin (it uses MinGW instead). This
          means ff can't pass it the name of a temp file as
          '/tmp/foo' because (on windows) /tmp is a cygwin fiction.
          So continue to put the file on cygwin's /tmp, but cd to
          that directory and then pass the bare filename.</li>

          <li>Add some more greek PUA small caps</li>

          <li>Add scroll bars to debug windows which lacked
          them</li>

          <li>Add a gloss window which explains what a ttf
          instruction is going to use and what it is going to
          do.</li>

          <li>Was using the wrong accent to build cyrillic
          breves.</li>

          <li>Remove the adobe private use defs from libgunicode
          and put them in fontforge.</li>

          <li>ff had problems reading pfm files containing kerning
          pairs using non-existant chars</li>

          <li>Add pixels per em in register view.</li>

          <li>No contours in twilight zone</li>

          <li>When generating tt fonts we did not set bit 8 in
          'head'.Flags. This gives bad results when ppem is not an
          integer</li>

          <li>When reencoding to adobe standard (or any encoding
          where glyph names are more important than code points)
          make sure we use glyph names rather than code points (so
          "f_i" is not in AdobeStd while "fi" is. But they map to
          the same code point).</li>

          <li>When creating a debug window in a glyph with no
          instructions (or in which 'gasp' has turned off hinting)
          we used not to rasterize it.</li>

          <li>Script/lang count was wrong in a number of
          places</li>

          <li>Oops, the transform dlg and menu both used the "round
          to int" string. Then I changed what it looked like in the
          menu, a change which is not appropriate for the transform
          dlg. Add a new string just for the dlg.</li>

          <li>Tavmjong Bah added something to the "ypogegrammeni"
          list.</li>

          <li>Fix problems with multiple text fields in the same
          window all wanting input contexts (for input
          methods).</li>

          <li>We generated ligature code in morx for ligatures that
          were not worth outputting.</li>

          <li>Pierre Hanser points out that a recent change to
          SetWidth broke the scritping SetWidth command.</li>

          <li>Yet more effort to remove rounding errors from remove
          overlap. If a control point causes a slight overshoot we
          get an unexpected extremum very close to one of the
          endpoints. If it's close enough this can cause problems.
          Tweak cps so this does not happen</li>

          <li>Solaris stores isnan &amp; friends in ieeefp.h not in
          math.h</li>

          <li>Add scripting access to standard math functions
          (trig, exp log)</li>

          <li>Unary minus didn't work on reals</li>

          <li>The recalculate bitmaps button in bitmap view was
          getting munched when we updated the cursor position.</li>

          <li>CharInfo("BBox") returned gibberish</li>
        </ul>
      </li>

      <li>9-Mar-2005

        <ul>
          <li>Deleting a glyph class within a kerning by classes
          object caused a crash</li>

          <li>Added some support for palm bitmap fonts</li>

          <li>Replace with reference only replaced the first
          instance.</li>

          <li>The Options dlg behaved oddly with respect to Apple
          &amp; OpenType modes</li>

          <li>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.</li>

          <li>When generating an opentype font from a script, and
          specifying flags, the round coordinates flag was
          ignored</li>

          <li>When generating a font from a script using the
          default flag setting, we would always generate
          afm/tfm/pfm files</li>

          <li>KANOU pointed out that the stroked font import glyph
          command only worked if multilayer set.</li>

          <li>Added a preview bitmap to eps files.</li>

          <li>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)</li>

          <li>Various fixes to make importing stroked eps files
          into stroked fonts work better.</li>

          <li>KANOU requests a preference item to turn off use of
          freetype in font view.</li>

          <li>Fix more rounding errors in remove overlap.</li>

          <li>Fix some problems in the routine which finds roots of
          an arbitrary quartic.</li>

          <li>The remove bump option of simplify could screw up
          memory.</li>

          <li>Remove overlap got unhappy about control points which
          caused a very tiny overlap between adjacent splines</li>

          <li>Redo from the fontview usually caused a crash.</li>

          <li>KANOU provides a MakeLine scripting command</li>

          <li>If TYPE3 (multilayer) was not enabled, there was a
          flow of control through a function which did not return
          anything.</li>

          <li>Recovery files did not contain multilayer marks which
          lead to strange behavior and crashes</li>

          <li>Converting a font to multilayer caused a crash if
          there were outline glyph windows open.</li>

          <li>Make the encoding for scripts be utf8
          consistently</li>

          <li>Allow the scripting Export command to take a format
          spec</li>

          <li>Add support for reals to the scripting language</li>

          <li>NearlyHv{Cps,Lines} scripting commands erroneously
          complained about too many args</li>

          <li>ff had a bug when outputting otf contextual
          ligatures</li>

          <li>Fix various crashes and infinite loops involved in
          parsing bad font files.</li>

          <li>ff had problems with user defined encodings.</li>

          <li>Made ff work if the psuedo-type "real" was defined to
          be a double.</li>

          <li>the string += concattonation operator in scripting
          screwed up memory</li>

          <li>Problems with -c &lt;arg&gt; syntax</li>

          <li>The font type detector could fail to notice an svg
          file as such if it began with a byte order
          character.</li>

          <li>Ord didn't do proper type checking on its second
          argument</li>
        </ul>
      </li>

      <li>9-Feb-2005

        <ul>
          <li>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).</li>

          <li>The bitmap dlg didn't work for multilayered fonts
          when told to use freetype to rasterize.</li>

          <li>If we had a contour nested inside another, and did an
          Overlap Exclude with the nested contour selected, then
          that contour was not excluded.</li>

          <li>The []Correct Direction check box when importing
          PostScript, didn't do anything. (or rather it did, but
          got overrulled later)</li>

          <li>In bitmap only fonts, bitmaps created without moving
          the width line would get lost.</li>

          <li>Added a scripting command "SelectByColor"</li>

          <li>Don't apply transformations to glyphs which aren't
          worth outputting</li>

          <li>Moving control points with the get point info command
          had problems in quadratic splines.</li>

          <li>When adding type42 support I broke multiple master
          support.</li>

          <li>Werner provided a patch to add a trailing newline to
          my type1 fonts.</li>

          <li>Support for PaintType==2 and stroked fonts.</li>

          <li>Various problems with the clustering command</li>

          <li>Oops, somehow a patch reverted and things didn't work
          on systems without iconv</li>

          <li>worked on a couple of other configuration problems
          for the mac</li>

          <li>Some people install libraries without headers. Be
          prepared.</li>

          <li>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.

            <p>So the script sub-table of both GPOS/GSUB should
            contain all scripts used in either (rather than just
            the scripts used in the current one).</p>
          </li>

          <li>The AddATT scripting command didn't understand
          Nested.</li>

          <li>Add a cli argument "-c" to introduce a scripting
          command in an argument.</li>

          <li>Someone ran ff on a solaris box without iconv. (Odd
          because iconv is there by default). FF ran fine (Odder,
          why didn't it demand the library?), but crashed when it
          tried to use a conversion which didn't exist.</li>

          <li>There's another ASCII map in Unicode
          (0xe0000-0xe007f).</li>

          <li>Allow user to supply their own OtherSubrs routines
          (Some people object to Adobe's copyright).</li>

          <li>Codes to handle identifying a loaded font by relative
          filespec didn't work.</li>

          <li>Change Add Extrema so that it only adds extrema if

            <ol>
              <li>The spline length is &gt;= em_size/32</li>

              <li>The extremum is an extremum of the entire contour
              containing the spline.</li>
            </ol>

            <p>(Behavior in the outline view when there is a
            selection remains the same. So if the endpoints of a
            spline are both selected then all local extrema will be
            added to that spline, no matter how long it may
            be).</p>
          </li>

          <li>Patch by Ralf Stubner. Fonts without UniqueID had a
          bad syntax.</li>
        </ul>
      </li>

      <li>17-Jan-2005

        <ul>
          <li>CapsLock now makes the arrow keys scroll in the
          outline view</li>

          <li>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,
          &lt;new-cnt+7&gt;/8 was different than
          &lt;real-cnt+7&gt;/8 and we ended up with garbage in the
          charstring.</li>

          <li>Add a TeX table to contain TeX metrics.</li>

          <li>TFM output was wrong. the TFtoPL doc says "</li>

          <li>reencoding with original encoding could create a
          glyph table one too small resulting in writing/reading
          garbage and an eventual crash.</li>

          <li>KANOU fixed a couple of problems in reading glyph
          names from bdf fonts.</li>

          <li>KANOU needed to disambiguate between "Point" a unit
          of measurement and "Point" a geometric object.</li>
        </ul>
      </li>

      <li>16-Jan-2005

        <ul>
          <li>Added support for OpenType Device Tables (These allow
          you to add small corrections to things like kerning at a
          given point size. Often at small point sizes kerning and
          advance widths will round in such a way as to produce
          unpleasing results. Device tables allow you to correct
          for that).</li>

          <li>Add dialogs for kerning pairs and anchors to allow
          users to set device tables. Extend dlg for kerning
          classes for this.</li>

          <li>Neil Parker suggested a patch for panose values that
          didn't apply to latin fonts</li>

          <li>Doing a Get Info on a single point caused a crash on
          the mac</li>

          <li>Further attempts to improve spline approximation,
          underlying Merge &amp; Simplify commands</li>

          <li>Relaxed simplify's definition of parallel so it will
          merge a few more straight lines.</li>

          <li>Make the behavior of Simplify More consistant across
          font/outline view. Simplify More can now set the default
          behavior for future simplify commands.</li>

          <li>Provide a menu command to round to hundredths of a
          em-unit</li>

          <li>Add a new facility to cluster coordinates to the same
          value. Useful as a prepass to Remove Overlap.</li>

          <li>Bug reading ligature data from a tfm file</li>

          <li>Add support for GPOS 'size' feature. Create a 'size'
          pane of the fontinfo dlg</li>

          <li>Replace with Reference had an interesting flaw.
          Consider the open and closed bullet characters. If the
          (single) contour in closed bullet matched the outer
          contour in open bullet then it would replace it with a
          reference. But this is incorrect as the two contours of
          open bullet need to be treated as a unit.</li>

          <li>Could get a bad memory reference in the font view if
          the mouse were to extend the selection outside of the
          window.</li>

          <li>Add a scripting function to return whether a file
          exists.</li>

          <li>In a Type1 font, if a glyph had no conflicting hints
          (and no flex hints) and got put in a subroutine, then
          we'd get no hints at all.</li>

          <li>Be more willing to generate format12 cmap subtables
          (unicode, non-bmp tables)</li>
        </ul>
      </li>

      <li>6-Jan-2005

        <ul>
          <li>New Copyright message, etc. Get rid of pfaedit
          message.</li>

          <li>Simplify produced strange results on quadratic
          splines.</li>

          <li>Simplify had problems with tangent points</li>

          <li>Changing a point's type from a tangent to a curve
          usually had unexpected results.</li>

          <li>Add a warning message in remove overlap when user
          passes us two intersecting contours which are oriented in
          oposite directions. Unfortunately it also complains about
          some other things.</li>

          <li>The 18 Dec changes to remove overlap introduced an
          infinite loop in some rare cases. (When there is a
          gradient of 0 in distance function between two
          splines).</li>

          <li>In a conditional operator (like &amp;&amp; or ||) in
          scripting where the second operand was not evaluated and
          the second operand contained a procedure call, then ff
          would crash</li>

          <li>Tweaked the point info dialog to show small offsets
          better</li>

          <li>Tweaked the merge command to behave better when
          merging tiny spline segments (where the length of the
          spline segment is so small that it should just be treated
          as a zero length spline and its slope ignored).</li>

          <li>Added an "Invert selection" command to the outline
          view, from Yoshiki Hayashi</li>

          <li>Pasting from the font view did not clear a glyph's
          instructions.</li>

          <li>New version of AutoHint. I've removed Diagonal Stem
          hints and mimum distance hints for now.</li>
        </ul>
      </li>

      <li>31-Dec-2004

        <ul>
          <li>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).</li>

          <li>ReplaceWithReference broke at some point</li>

          <li>Add an argument-pair to the ReplaceWithReference()
          scripting command to allow the user to specify the amount
          of error that will be accepted.</li>

          <li>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.</li>

          <li>Upgrade to Adobe-Japan1-6</li>

          <li>Various fixes to svg output

            <ul>
              <li>export glyph to svg didn't work</li>

              <li>multilayered generation had problems</li>
            </ul>
          </li>

          <li>Ghost hints could get outside a glyphs bounding box
          in a type2 font.</li>

          <li>The generated truetype unique id string had an off by
          one error in the month</li>

          <li>Add support for dashed lines in multilayered
          mode</li>

          <li>In Full Page Glyph printing, the glyph was offset
          slightly from where it should have been.</li>

          <li>Pasting a reference into a multi-layered font
          produced a very odd layer</li>

          <li>ff didn't update the metrics view if the user pasted
          the selection with the middle mouse button.</li>

          <li>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)</li>

          <li>Make the behavior of control points at the ends of
          open paths more reasonable.</li>

          <li>The Point-&gt;Curve command did not adust control
          points correctly.</li>

          <li>The View-&gt;Display Substitutions had numerous
          problems.</li>

          <li>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.</li>

          <li>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.</li>
        </ul>
      </li>

      <li>18-Dec-2004

        <ul>
          <li>Added a raster debugger wndow</li>

          <li>Each time debugger starts, remember what debug
          windows were open last time it was used.</li>

          <li>Constraining the pen tool did not do what I
          expected</li>

          <li>If a glyph was encoded twice (or more) in a font, and
          an opentype font (or perhaps a bitmap only sfnt) were
          generated, then any glyphs after the second encoding
          would have the wrong width (ie. there would be an extra
          entry in the horizontal metrics table corresponding to a
          (non-existant) copy of the doubly encoded glyph)</li>

          <li>If a type1 font never defined .notdef but used it at
          least twice it the Encoding vector, then ff would
          crash.</li>

          <li>Updated Japanese UI (by KANOU)</li>

          <li>Werner found some crashes related to calling isalnum
          (etc.) using an index outside of bmp.</li>

          <li>More changes (I hope improvements) to remove
          overlap</li>
        </ul>
      </li>

      <li>13-Dec-2004

        <ul>
          <li>Some fixes to the raster display of the debug
          window</li>

          <li>Conversion of cubic to quadratic had a rounding error
          introduced by -O2. Made it a bit more forgiving about
          rounding errors.</li>

          <li>Added two new buttons to the point info dialog to
          allow the user to walk around the current contour
          (Normally the Next button skips to the start of the next
          contour if you are at the end of the current one, the
          "Next On Contour" button returns to the first point on
          the contour)</li>

          <li>improve interpretation of some type3 fonts (including
          those produced by fontographer 4)</li>

          <li>patch by Yoshki Hayashi to fix mnemonic crash in
          layers palette</li>

          <li>Added a rand() scripting command</li>

          <li>Support backslash newline to break up lines in a
          scrpt</li>

          <li>The internal adobe standard encoding thought it was
          unicode causing strange effects</li>

          <li>Type3 fonts that set colour/grey didn't work</li>

          <li>Printing at 140pt tried printing 4 glyphs across
          although there was only room for 3</li>

          <li>At install tell pkg-config the verson of
          fontforge</li>
        </ul>
      </li>

      <li>3-Dec-2004

        <ul>
          <li>If a cff file contained unencoded glyphs then ff
          would crash when loading it.</li>

          <li>When converting from cubic to quadratic splines, ff
          would sometimes produce a line when it should have found
          a spline</li>

          <li>During debugging of a ttf glyph, show what
          rasterization would produce if the current splines were
          used (highlight pixels which change)</li>

          <li>The debugger windows didn't always say
          "&lt;empty&gt;" when they should have.</li>

          <li>The debugger would often crash the second time we
          closed its window</li>

          <li>Asking for the script (as latin, greek, cyrillic...)
          of ".notdef" caused us to look at unallocated
          memory.</li>

          <li>We weren't labelling control points in the
          debugger</li>

          <li>debugger and grid fitter for tt fonts showed curved
          splines as lines</li>

          <li>Kerning pairs did not get scaled when changing
          em-size</li>

          <li>Add a preference for turning off automatic gotos as
          the user types in the glyph window</li>

          <li>Add a command to the glyph window to toggle between
          the two most recent glyphs used in that window (a mini
          history)</li>

          <li>Improved the points debugger window to show

            <ul>
              <li>implied points</li>

              <li>whether a point is on or off the curve (normal or
              control)</li>

              <li>added a scroll bar</li>
            </ul>
          </li>

          <li>Provide info on debugging points as mouse moves over
          them.</li>

          <li>Fix (an innocuous) reference to unallocated
          memory</li>

          <li>Added ability to insert an uninterpreted table into
          an SFNT

            <ul>
              <li>New preference item: PreserveTables which lists a
              comma separated set of table tags which are to be
              loaded from SFNT files without interpretation (Note
              if ff thinks it understands a table it will parse it
              rather than preserving it)</li>

              <li>Scripting command LoadTableFromFile("tag
              ","filename")</li>

              <li>Scripting command SaveTableToFile("tag
              ","filename")</li>

              <li>Scripting command RemovePreservedTable("tag
              ")</li>

              <li>Scripting command HasPreservedTable("tag ")</li>
            </ul>
          </li>
        </ul>
      </li>

      <li>22-Nov-2004

        <ul>
          <li>Kevin Schoedel suggests a new scripting command
          DrawsSomething()</li>

          <li>Kevin Schoedel requests that PrintFont be able to
          print a string sample (as opposed to a sample file)</li>

          <li>Kevin Schoedel points out that type1 fonts stuffed
          into mac resource forks are to be read in resource order
          rather than file order (often the two are the same) and
          provides a patch to fix this.</li>

          <li>Change the way the default language/locale is picked
          in fontinfo-&gt;TTF Names</li>

          <li>Remember (across invocations) whether palettes should
          be hidden or not.</li>

          <li>Ignore NUL chars when reading PostScript strings (PS
          supports NULs in strings, I'm not going to bother, but I
          don't want to parse incorrectly because of them).</li>

          <li>ff lost the ability to Select("U+xxxx") or
          Select("=") from a script.</li>

          <li>Oops, the routine to read PostScript FontNames from a
          ttf file was broken by the encoding change.</li>

          <li>If a ttf file contained an erroneous composite glyph
          with flags indicating more components after the glyph had
          run out of data, then ff might attempt to read
          instructions also and have problems.</li>

          <li>If a font contains multiple ttf names for a given
          string in a language then allow the user to pick which
          one s/he likes best.</li>

          <li>Another case where a bad otf table crashes
          fontforge</li>

          <li>If a ttf/otf font does not contain a postscript
          FontName string in the name table, then ff's attempt to
          synthesize one out of fullname/familyname did not check
          for a valid name.</li>
        </ul>
      </li>

      <li>15-Nov-2004

        <ul>
          <li>If ff started without a prefs file, then creating a
          new font would crash</li>

          <li>If a copyright string contained a newline then ff
          would generate bad postscript</li>

          <li>If user added a comment to an empty glyph then the
          comment wasn't saved in the sfd file.</li>

          <li>If ff saved a utf7 string to an sfd file (ttf names,
          etc.) and that string contained a hyphen that followed
          immediately after something that needed to be encoded in
          base64, then the hyphen would be lost.</li>

          <li>new french UI</li>

          <li>ff was (usually) setting the ascent/descent fields of
          the 'hhea' table to 0. When the font was drawn on the mac
          it was clipped to nothing. <span class="c2"><strong><big>
            Caveat: Old sfd files are still broken and there is no
            UI for fixing them. Instead you must edit them
            manually, and change:</big></strong></span>
            <pre>
HheadAOffset: 0
HheadDOffset: 0
</pre>

            <p>to be:</p>
            <pre>
HheadAOffset: 1
HheadDOffset: 1
</pre>
          </li>
        </ul>
      </li>

      <li>12-Nov-2004

        <ul>
          <li>ff would crash on postscript fonts where the encoding
          included a glyph name not defined in CharStrings
          (probably broken on 12-Oct)</li>

          <li>More remove overlap work</li>

          <li>In the glyph window, when the scaled distance between
          the top and bottom of the window is less than 1 em-unit,
          then the vertical ruler was drawn with the top and bottom
          labels reversed.</li>

          <li>sfd files used to have a limit of 1023 characters in
          ttf 'name' table strings.</li>
        </ul>
      </li>

      <li>6-Nov-2004

        <ul>
          <li>Encoding change broke prefs dialog</li>
        </ul>
      </li>

      <li>5-Nov-2004

        <ul>
          <li>Encoding change didn't work on libiconv systems</li>
        </ul>
      </li>

      <li>4-Nov-2004

        <ul>
          <li>Added a new scripting command: AddAccent() to add an
          arbitrary accent to an arbitrary glyph.</li>
        </ul>
      </li>

      <li>3-Nov-2004

        <ul>
          <li>KANOU has a <a href=
          "http://khdd.net/fontforge-jman/">Japanese version</a> of
          this reference manual under construction.</li>

          <li>In MultiLayered mode, the "New Layer" menu item left
          a dangling pointer which caused a crash if anyone looked
          at the background layer.</li>

          <li>In MultiLayered mode, if one clicked beyond the last
          layer in the Layers palette, ff would crash.</li>

          <li>KANOU provided a patch to fix another crash in the
          layers palette.</li>

          <li>KANOU has provided a new Japanese UI.</li>

          <li>Made an addition to CharInfo() scripting command so
          user can determine the horizontal extrema of a glyph at a
          given vertical position. Similar addition for vertical
          extrema at horizontal pos.</li>

          <li>Add a scripting command (PasteWithOffset) to allow
          user to apply an offset when pasting. For building
          accented letters by hand.</li>

          <li>KANOU provides a patch to fix a problem in the new
          encoding stuff.</li>

          <li>Select(".notdef") usually didn't work.</li>
        </ul>
      </li>

      <li>28-Oct-2004

        <ul>
          <li>Kanou noticed that ISO 15924 has been updated and
          provide a patch including new scripts.</li>

          <li>I have redone the way ff handles encodings
          internally. We used to depend on the encodings builtin to
          gdraw/gunicode. Now we use iconv() (if there is no iconv,
          then ff will use a dummy iconv which understands the
          encodings of gdraw/gunicode). Encodings are identified by
          name rather than by number now.</li>

          <li>Further fixes to the extremum detector</li>

          <li>Further fixes to remove overlap</li>

          <li>Added an extra argument to scripting RoundToInt, so
          that you can have control over what it rounds to (ie.
          round to hundredths, tenths, etc.)</li>

          <li>Added two new scripting commands NearlyHvCps() and
          NearlyHvLines() which look for control points or lines
          that are nearly horizontal or vertical and force them to
          be horizontal or vertical.</li>

          <li>Kanou provided a patch so that the GRadio.Font
          resource controls the font in the layers palette of the
          glyph view.</li>
        </ul>
      </li>

      <li>23-Oct-2004

        <ul>
          <li>Remove overlap had problems with splines which made
          abrupt turns (ie. tiny splines after we found extrema
          points and divided the spline into bits between
          extrema)</li>

          <li>Remove overlap could munch memory</li>

          <li>The ruler tool showed all tiny splines as having a
          length of 0</li>

          <li>Autorecovery had problems with glyphs containing
          features (would complain about sli)</li>

          <li>KANOU wants to be able to scale greymap fonts</li>

          <li>removed routines from fvcomposit.c, metricsview.c
          that were duplicates of fvfonts.c</li>

          <li>Oops, the default mac filesystem isn't case concious
          either, extend the windows export patch to the mac.</li>

          <li>Simplify didn't have a very good extremum detector
          and would sometimes delete extrema.</li>
        </ul>
      </li>

      <li>14-Oct-2004

        <ul>
          <li>Remove overlap had problems with tiny splines.</li>
        </ul>
      </li>

      <li>13-Oct-2004

        <ul>
          <li>I notice (in Fontes &amp; Codages) that the labels in
          the metrics view aren't translatable</li>

          <li>Fontes &amp; Codages suggests that it would be nice
          if the glyph labels in the fontview could be something
          other than an image of the glyph (glyph name, unicode
          code point, encoding, etc.)</li>

          <li>Change the word "Character" to "Glyph" where
          appropriate.</li>

          <li>Move the Open Outline/Bitmap/Metrics commands to the
          Window menu, and change "Open" to "New".</li>
        </ul>
      </li>

      <li>12-Oct-2004

        <ul>
          <li>We have a Spanish UI now, courtesy of Walter Echarri.
          Yeah!</li>

          <li>Support for loading type3 fonts (that ff produced)
          was broken. Note: ff is still unable to load many type3
          fonts (any that are filtered, or that use images for
          example), but it should be able to read its own
          fonts.</li>

          <li>(I hope) minor change to the way .notdef is handled
          when reading postscript files.</li>

          <li>Added support for printing to pdf file</li>

          <li>(fixed a bug in pdf generation from the export
          command)</li>

          <li>Fixed various problems from turning off the
          multilayer bit in fontinfo</li>

          <li>KANOU needs a couple more strings disambiguated.</li>

          <li>Add support for generating type42 and type 11 (type42
          cid) fonts, add support for loading type42 (but I'm not
          bothering with type11s) and use these guys when printing
          order2 fonts.</li>

          <li>Check to make sure the PostScript Fontname is valid
          when reading in a truetype (or svg) font (syntax doesn't
          enforce this), and if not warn the user and fix it
          up.</li>

          <li>Add some new scripting commands for handling MM fonts
          since someone seems to want them.</li>

          <li>Used to complain if there were more than one Unique
          Font ID in the truetype 'name' table. (because the
          OpenType list said there should only be one, else it
          would not be unique). But both Apple and MS ship with
          fonts containing multiple Unique Font IDs. God knows what
          that means, or when you pick one over the other... Anyway
          I changed my error into a warning.</li>
        </ul>
      </li>

      <li>30-Sept-2004

        <ul>
          <li>I have rewritten Remove Overlap from scratch. I seems
          less likely to crash, but I'm not sure that in any other
          respect it is improved.</li>

          <li>In the character view the Remove Overlap (and
          Intersect and Find Intersections) now only work on
          selected contours, or, if no contours are selected then
          on all contours. This change makes these commands
          consistant with most other commands in the character
          view, but it is a change from past behavior.</li>

          <li>The Import scripting command has been extended to
          give the user control over the stroking flags (correct
          direction, remove overlap, handle erasers). And the
          background flag has been extended a bit to apply to other
          things than bitmaps.</li>

          <li>ff had a pointer dangling to a freed block after
          loading a font containing multiple versions of some greek
          letters.</li>

          <li>U+1D400-U+1D7FF are stylized variants of the latin
          and greek alphabets as used in Mathematics. The font view
          will now display (in the glyph header) the proper variant
          of the glyph (assuming it can find a font with that
          style).</li>

          <li>The AMS (American Mathematical Society) has their own
          interpretation of the public use area. FF now understands
          their glyph names as alternates for those glyphs, and has
          an AMS interpretation (under FontInfo-&gt;Encoding) that
          will make ff use those names in new fonts.</li>

          <li>Many of code points in the AMS PUA are reencodings of
          other glyphs. FontForge will automatically generate these
          reencodings for you.</li>

          <li>The AMS also describes how some TeX glyph names map
          to unicode. So include those names in our alternate list
          too (so we can map them correctly, not as a way of
          encouraging people to use them).</li>

          <li>Both the AMS defn. of the PUA and the Big5 defn. map
          characters which are properly in other unicode planes
          into the BMP. FF now understands this, and converting
          between a BMP encoding and a full unicode encoding will
          move things from the PUA to their proper unicode slot in
          higher planes.</li>

          <li>Find Problems thought that adjacent splines
          intersected at their common end-point. I suppose they do,
          but it isn't useful information</li>

          <li>In the char view, I used to blank out the status line
          when the mouse moved outside the window. But some of that
          info is still valid. So only blank out the meaningless
          bits.</li>

          <li>Kanou requests a disambiguation between two strings
          with the same label in English but different meanings in
          Japanese. (Vertical/VerticalWriting)</li>

          <li>The Point-&gt;Make Line command would crash if either
          of the two points was missing a previous or next
          spline.</li>

          <li>Pierre HANSER provides a patch to problems.c (it
          would crash when dealing with fonts with an encoding with
          &lt; 32 code points.</li>

          <li>Pierre HANSER provides a patch to merge fonts (it
          would crash when merging bitmap fonts.</li>

          <li>Closing a charview window with a docked palette could
          cause a crash if the cursor was moved quickly into
          another charview which needed a new cursor.</li>

          <li>The perspective icon had the wrong background</li>

          <li>Piska keeps complaining about the way ff handles 0
          width strokes. He wants it to have zero width (disappear,
          I guess), but PS says it should be stroked as the
          thinnest line possible (not clear what this should mean
          in ff, I interpret it as a 1em-unit stroke). But METAPOST
          uses a 0 width stroke in cases where it wants no stroking
          (with a fill) so in the special case of a fill with a 0
          width stroke, turn off stroking.</li>

          <li>Use a different approach to approximating a set of
          points with fixed slopes at the end points. Used to do
          least squares (fixup slopes), least squares again (fixup
          slopes). Now I do least squares (fixup slopes), perturb
          the lengths of the slope vectors until we find the best
          fit.</li>

          <li>I was generating flex hints when I should not have
          done so. Add a heuristic so that ff doesn't add flexes to
          small circles.</li>

          <li>Failed to read long format pk bitmaps.</li>

          <li>Patch by Mchael Ghrken to make the Skew scripting
          command take a numerator/denominator style argument.</li>
        </ul>
      </li>

      <li>24-Aug-2004

        <ul>
          <li>Oops, didn't get the expand stroke scripting patch
          quite right</li>

          <li>
            <span class="c2"><strong><big>Changed the way
            preferences are handled in
            scripts</big></strong></span>

            <ul>
              <li>By default preferences are no longer loaded when
              starting a script.</li>

              <li>Preferences are not saved in a script unless
              explicitly requested.</li>

              <li>Added 2 new scripting functions LoadPrefs() and
              SavePrefs()</li>

              <li>Added an environment variable FONTFORGE_LOADPREFS
              to give the user control over loading of
              preferences.</li>
            </ul>
          </li>

          <li>Used to have a preference item DumpGlyphMap. Now we
          have an equivalent flag in the Generate Fonts [Options]
          dialog.</li>

          <li>The SetPanose scripting command didn't work. MURAOKA
          Taro provides a patch</li>

          <li>It was not possible to get or set NewCharset
          preference item with GetPref/SetPref scripting commands.
          Now GetPref returns a magic number, which may be used in
          SetPref. SetPref will accept either a number or one of
          the encodings accepted by Reencode().</li>

          <li>If you copied a glyph feature from a glyph that
          didn't have that feature, and then did a paste ff would
          crash.</li>

          <li>Added two new tools to the outline character view.
          One allows you to rotated your glyph through 3dimensions
          (and project it back on the xy plane), the other allows
          you to do a perspective transformation.</li>

          <li>Extended the Transformation dialog to handle 3D
          rotation+projection. After all it's just:

            <table border="1" cellpadding="2" align="center">
              <tr>
                <td>cos(y-axis-rotation)</td>

                <td>
                  <p class="c3">0</p>
                </td>
              </tr>

              <tr>
                <td>
                  <p class="c3">0</p>
                </td>

                <td>cos(x-axis-rotation)</td>
              </tr>
            </table>
          </li>

          <li>Add a Point of View dialog to do real perspective
          projections</li>

          <li>Remove the FONTFORGE_CONFIG_NONLINEAR flag, and
          enable the nonlinear dlg perminantly. I need some of its
          routines to do the perspective projections.</li>

          <li>There was a path through LoadEncodingFile (in a
          script) where it would silently fail.</li>

          <li>LoadEncodingFile would save default encodings even
          though it hadn't loaded them. It no longer does this, but
          now SavePrefs does it instead.</li>

          <li>Added the ability to see (and create) simple
          substitutions in the font view.</li>

          <li>The embossed box around the fontinfo dlg wasn't
          always in the right place</li>
        </ul>
      </li>

      <li>8-Aug-2004

        <ul>
          <li>Zhang Lin-bo reports two bugs (which were really
          three)

            <ul>
              <li>Expand Stroke failed when given a path consisting
              of a single point had a zero length spline returning
              to itself.</li>

              <li>AddExtrema falls into an infinite loop if the
              initial spline of a path needs an extremum added to
              it.</li>

              <li>Expand Stroke generates garbage output in some
              very obscure conditions.</li>

              <li>AutoHint crashes when given garbage input.</li>
            </ul>
          </li>

          <li>Michael Gährken points out that ExpandStroke
          scripting command doesn't work for caligraphic stroking,
          provides a patch and an extension.</li>

          <li>KANOU provides a patch for BDFMakeChar in CID keyed
          fonts.</li>

          <li>Change the Shades palette in the bitmap view so that
          it shows what grey level is underneath the cursor.</li>

          <li>When the width is huge, then moving it causes it to
          wrap into negative values. It should probably stick at
          SHRT_MAX instead.</li>

          <li>If one moves to a negative width and releases the
          mouse, an error message pops up warning of this. If you
          move the cursor around the width continued to
          change.</li>

          <li>If one moves to a negative width, and in response to
          the width warning says [No] then the width reverted to
          the wrong value.</li>

          <li>ff would crash on a postscript sequence containing
          "{}" if that was the first function defined.</li>

          <li>I got the locale wrong for Hong Kong</li>

          <li>If nothing was selected in the import dlg (or any of
          the file open dlgs) and the user pressed [OK], then the
          directory would be returned.</li>

          <li>Improved error message for Import dlg.</li>

          <li>In spanish various dlgs had buttons that were too
          close together (and similar problems)</li>
        </ul>
      </li>

      <li>01-Aug-2004

        <ul>
          <li>ff did not generate amfm files correctly</li>

          <li>Changed the Merge Kern Infor (menu item and scripting
          command) to

            <ul>
              <li>support pfm files</li>

              <li>detect file type from the file header rather than
              from the extension</li>
            </ul>
          </li>

          <li>Added InterpolateFonts as a scripting command</li>

          <li>Added GetEnv as a scripting command</li>

          <li>The scripting $fontversion and $copyright psuedo
          variables broke when I added the fond name changes.</li>

          <li>More problems with tfm files.</li>

          <li>Fixed a couple of problems related to dialog sizing
          for different languages.</li>

          <li>In Windows 3.1 some chinese fonts were released with
          a ttf version of 2 (rather than 1). Add this to the list
          of supported TrueType/OpenType versions (see discussion
          on freetype mailing list, july 2004 for more info)</li>

          <li>Added both a menu and scripting command to copy
          kerning &amp; substitution info from one glyph to
          another.</li>

          <li>FontForge fails to load some svg fonts properly (if
          they use the "t" directive within a path =&gt; quadratic
          splines, control point implied, relative to last point).
          Result is a nasty scribble.</li>

          <li>Windows file systems are not case conscious. The file
          names generated for Export use glyph names (which are
          case conscious). So on windows exporting "a" and "A" will
          overwrite the same file. (Add a "$" in front of capital
          letters to distinguish).</li>

          <li>We were not scaling refs/images uniformly when we
          dragged corners. Instead we changed the sides by the same
          amount (this works for squares, but nothing else).</li>

          <li>XML does not allow backspace as an input character,
          even when specified by an entity. This means we can't
          specify the unicode code point for backspace in a an svg
          font (and many ttf fonts contain a blank backspace char,
          god only knows why).</li>

          <li>The Default ATT-&gt;Unicode decomposition didn't
          work.</li>

          <li>Added a new entry to Default ATT, Caps-&gt;Small Caps
          (and cleaned up lower case-&gt;small caps too).</li>

          <li>Eschew 0 width hints.</li>

          <li>Add support for localized unicode glyph names
          (currently only french is available)</li>
        </ul>
      </li>

      <li>3-July-2004

        <ul>
          <li>Undoes in the Guide layer caused a crash (introduced
          with multi-layer)</li>

          <li>Fixed another problem with subroutine references in
          type1 output</li>

          <li>Preserve hhea.ascent/descent and some OS/2 values (no
          UI for these, but they are retained)</li>

          <li>KANOU provided two patches

            <ul>
              <li>One to set the average Char Width field of OS/2
              properly</li>

              <li>One to set the 'gasp' table so that Windows would
              actually use embedded bitmaps</li>
            </ul>
          </li>

          <li>Added support (in build accent) to look for upper
          case and cyrillic variants of accents (use grave.cap
          rather than grave, use breve.cyr rather than breve) when
          building upper case or cyrillic letters.</li>

          <li>Points were not being properly renumbered if they
          were out of order (when editing in quadratic mode)</li>

          <li>When a character had a color attached to it, it
          looked very strange if the user changed it.</li>

          <li>Added an "x" to check boxes when checked</li>

          <li>FF did not realize that tonos should be treated as an
          accent (it is spacing, which confused ff)</li>

          <li>Cleaned up an ancient message in the nomen files.
          Used to be three separate strings, now one with format
          specs in it.</li>
        </ul>
      </li>

      <li>18-June-2004

        <ul>
          <li>Point types were not set properly after conversion
          from quadratic to cubic splines.</li>

          <li>Several preference items were not being saved and
          were not accessable from scripts.</li>

          <li>Scripts could not set the resolution for bdf
          fonts</li>

          <li>Still having problems with references to references
          in type1 subroutines.</li>

          <li>AutoTrace had problems with multi-layered mode.</li>

          <li>Enhance "ItalicConstrained" in the Character View to
          allow vertical constrains as well as those parallel to
          the italic angle.</li>

          <li>Build Accented Characters had problems when there
          were bitmap characters involved.</li>

          <li>Can no longer blindly rotate splinesets in type2
          fonts to avoid an initial flex.</li>

          <li>Add three new problems to Find Problems

            <ul>
              <li>Check for intersecting contours</li>

              <li>Check for mulitple glyphs with same unicode code
              point</li>

              <li>Check for multiple glyphs with same name</li>
            </ul>
          </li>
        </ul>
      </li>

      <li>31-May-2004

        <ul>
          <li>In the 19-May build I introduced a bug which could
          generate NaN values for control points.</li>
        </ul>
      </li>

      <li>29-May-2004

        <ul>
          <li>The MergeKern scripting command didn't have the
          capabilities of its menu counterpart.</li>

          <li>Enhance the pattern matching capabilities on font
          names when loading kerning information from a mac FOND
          (there is no place in the FOND that names the styles, so
          best we can do is make reasonable guesses).</li>

          <li>When editing quadratic fonts (truetype), changing the
          type of a point to be a tangent caused the previous
          control point to be set the to same location as the next
          control point. Bleah.</li>

          <li>New versions of libpng will not automagically load
          libz when they are loaded. Needed a patch to load libz
          manually.</li>

          <li>Fixed a couple of bugs in contextual / chaining
          dialog.</li>

          <li>When reading PostScript arrays FF failed to parse
          negative numbers properly.</li>

          <li>Make it an error (which it should be) to create a mac
          postscript resource file without also generating an
          NFNT.</li>

          <li>Warn that NFNTs don't work under OS/X, warn that POST
          resources are probably deprecated.</li>

          <li>WinAscent/Descent were being saved incorrectly in sfd
          files, leading to bad WinAscent/Descent in t/otf OS/2
          tables.</li>

          <li>Crash in ExpandStroke from a NaN when try to
          intersect parallel lines</li>

          <li>Improved Merge a little bit for quadratic
          splines</li>
        </ul>
      </li>

      <li>23-May-2004

        <ul>
          <li>Added popups in the Open Font dialog to show the
          fontname(s) of any font(s) in a file.</li>

          <li>FontForge failed to load background images. A bug
          introduced 24-Feb (part of multi-layer)</li>

          <li>Reordered the which glyph FF would pick when
          searching for accents. It used to use ASCII versions of
          the accents over those in the U+03xx range.</li>
        </ul>
      </li>

      <li>20-May-2004

        <ul>
          <li>Bug in scripting change for mac families.</li>

          <li>Added a Paste After command (which isn't visible by
          default) which will allow you to build up words more
          easily.</li>
        </ul>
      </li>

      <li>19-May-2004

        <ul>
          <li>Give the user access to the OS/2 fields WinAscent and
          WinDescent.</li>

          <li>Add a new command (Points-&gt;Make Line) which will
          turn a spline between two selected points into a
          line.</li>

          <li>Improve the behavior of defaulting control points so
          we don't get self-intersecting loops</li>

          <li>Add a mode to the pointer tool. Holding down the
          &lt;Alt&gt; key now means we don't join two open contours
          if they make contact while dragging.</li>

          <li>When loading an otf file and saving it as ttf,
          sometimes the space glyph would become zero width.</li>

          <li>Redid the way mac families were output. Should be
          more flexible under OS/X</li>
        </ul>
      </li>

      <li>9-May-2004

        <ul>
          <li>Several problems with tfm files. Didn't handle tfms
          with more that 128 lig/kerns.</li>

          <li>Failed to set the r2l flag properly in 'morx'
          tables</li>

          <li>More typos in the ghost hint code</li>

          <li>Allow users to express error term of the scripting
          Simplify command as a fraction.</li>

          <li>The strings in the context / chaining dlg's initial
          pane were wrong</li>

          <li>Fixed some bugs in converting OT contextual
          substitutions to Mac state machines</li>

          <li>If we wanted to put a glyph with references into a
          subroutine (in type1 output) we failed miserably</li>

          <li>Added a new command <a href=
          "editmenu.html#ReplaceRef">Edit-&gt;ReplaceWithReference</a>
          (and a scripting version too), which searches all glyphs
          in the font for any selected glyphs, and for each
          embedded occurance it replaces the outlines of the glyph
          with a reference to it. This is because reading a
          postscript (type2 or type1) font generally loses all
          reference information.</li>

          <li>The documentation for OS/2.winAscent makes no sense.
          I shall ignore it and set winAscent to hhea.ascent</li>

          <li>Sivan says that hebrew kerning is broken again.</li>

          <li>The search dlg didn't work on quadratic (truetype)
          fonts</li>
        </ul>
      </li>

      <li>2-May-2004

        <ul>
          <li>I've changed the colour of check boxes because people
          found black confusing</li>

          <li>FontForge read Italic Correction incorrectly out of
          tfm files and had minor problems generating tfm
          files.</li>

          <li>the kern class dlg had an uninitialized variable
          (introduced with the multiple master code I think)</li>

          <li>FontForge would sometimes crash when generating a
          GDEF table for some types of otf font.</li>

          <li>Pierre Hanser has updated the french UI, and pointed
          out some problems with the english UI.</li>

          <li>In a version of FontForge compiled with MultiLayer
          on, Pasting something containing a reference screwed up
          memory</li>
        </ul>
      </li>

      <li>25-Apr-2004

        <ul>
          <li>AutoHint produced ghost hints for curved stems that
          sometimes were outside of the character.</li>

          <li>Fixed some uninitialized variables in MetaFont (but
          the algorthim is still flawed)</li>

          <li>FontForge had problems when the fontview was
          maximized.</li>

          <li>The 18-Apr patch for cubic-&gt;quadratic conversion
          had a bug which generally resulted in a crash.</li>

          <li>When flickering in and out of compacted mode, during
          a Generate Fonts, the encodings in the displayed bitmap
          could get out of sync with those of the font leading to a
          crash.</li>

          <li>Don't mess with the control points in point type
          conversion (corner-&gt;curve/tangent) when the they are
          already reasonable.</li>

          <li>Allow rectangles and ellipses to have separate
          settings of the center out flag.</li>

          <li>Add a dialog which allows you to specify exactly
          where rectangles/ellipses should go.</li>

          <li>Double-clicking on the scale/flap/rotate/skew tool
          brings up the transform dialog.</li>

          <li>Add a couple of entries in the transform dlg option
          menus which copy information from the last ruler
          measurement.</li>

          <li>Give the user control over how long the ruler window
          hangs around.</li>
        </ul>
      </li>

      <li>18-Apr-2004

        <ul>
          <li>Fix a couple of bugs dealing with references in
          multilayered editing.</li>

          <li>Uninitialized variable in creation of 'name' table
          (introduced on 10-Apr)</li>

          <li>Edit-&gt;Merge didn't work properly on quadratic
          splines</li>

          <li>LCarets should have ignored the script assigned to
          them, but they didn't.</li>

          <li>Put in more protection against bad GSUB/GPOS tables.
          In particular mangal.ttf has a bad GSUB table (with
          erroneous class specifications).</li>

          <li>FontForge wasn't setting
          <tt>'hhea'.caretSlopeRun</tt> appropriately in italic
          fonts (should match <tt>tan(italicAngle)</tt>).</li>

          <li>Oops. Can do much better converting from cubic to
          quadratic splines. We were getting far too many linear
          segments.</li>

          <li>Our cubic-&gt;quadratic conversion could generate
          splines where the endpoints were less than 1 unit apart.
          Since ttf rounds all coords to ints, this meant we'd get
          the two endpoints on top of one another.</li>

          <li>When generating a truetype font from a cubic
          database, FontForge calculated 'maxp'.maxCompositePoints
          incorrectly.</li>

          <li>Gave the user control over when point numbers are
          visible (even for cubic fonts)</li>
        </ul>
      </li>

      <li>10-Apr-2004

        <ul>
          <li>The flatten commands didn't preserve the ttf 'name'
          table nor the 'OS/2' table</li>

          <li>Redid the way 'name' table was generated, hopefully
          we do better for the mac now.</li>

          <li>the 'kern' table had a bad rangeShift value (it was
          the negative of what it should be)</li>

          <li>Pasting a reference from one font to another could
          crash if the destination font did not have the refered
          character.</li>

          <li>".null" was appearing twice in the 'post' table when
          saving a ttf file a second time.</li>

          <li>Markus Schwarzenberg points out that the ScaleToEm()
          scripting command didn't work when given a single
          argument.</li>

          <li>Pierre Hanser points out that the version fix on
          4-Apr had a bug that caused crashes on Macs (perhaps
          elsewhere).</li>
        </ul>
      </li>

      <li>04-Apr-2004

        <ul>
          <li>Several more fixes for cff output.</li>

          <li>We had a bad habit of including extraneous hintmask
          operators in output</li>

          <li>Add a proper ff version (well, as much as my versions
          be proper) to postscript/svg output</li>

          <li>Patch from Kanou about reading format 2 bitmaps in a
          sfnt</li>

          <li>Patch from Kanou. MS requires a weird format for GSUB
          in vertical writing.</li>
        </ul>
      </li>

      <li>29-Mar-2004

        <ul>
          <li>When Type1 output needed to output a reference as
          inline splines (as opposed to a subroutine call or using
          a seac command) then it would lose any translation
          applied to that reference.</li>

          <li>Patch to Type3 output from R.L.Horn</li>

          <li>FontForge used to crash when reading in a bdf glyph
          with a bad bounding box.</li>

          <li>Reading a kerning class from an sfd file when that
          class had more second character classes than first
          character classes would screw up memory and probably
          cause a crash.</li>

          <li>Attempting to edit a 'cvt ' table in a font without
          one caused a crash. Attempting to edit a 'cvt ' table in
          a font with one showed an empty table.</li>

          <li>Make scaling from the fontview apply to kerning and
          positioning data.</li>

          <li>Drawing a rectangle by dragging from center out
          didn't work</li>

          <li>Display phantom points when debugging. Be prepared to
          find either 2 (horizontal metrics) or 4 (both horizontal
          or vertical) depending on what version of freetype we've
          got.</li>

          <li>Bug in both reading and writing encoding format 0 of
          cff fonts. I forgot to ignore .notdef so everything was
          off by 1.</li>

          <li>If a glyph was used as a reference in another glyph,
          and we put it in a subroutine (type1 output), and it had
          hint conflicts, then the first group of hints never got
          output.</li>

          <li>In multilayered mode, the Revert Glyph command left
          memory in a potentially bad state. (If you immediately
          closed the charview, then nothing bad would happen, but
          if you tried any editing in it, then nasty things
          happened.)</li>
        </ul>
      </li>

      <li>21-Mar-2004

        <ul>
          <li>When flattening a CID file fontforge lost track of
          the script/lang list (and other things) which caused bugs
          when dealing with substitutions</li>

          <li>When saving multiply, fontforge could free a fonts
          hash table several times</li>

          <li>When flattening by a CMAP file from a script
          fontforge could crash</li>

          <li>Added a CIDFlatten command to scripting.</li>

          <li>The "cleanup of OS/2" on 29-Feb actually broke
          WinAscent/Descent</li>

          <li>When loading a mac unicode string from the 'name'
          table, fontforge failed to convert the language
          correctly.</li>

          <li>When loading a mac contextual substitution
          statemachine, fontforge made egregious errors in guessing
          to what glyphs were usable for a substitution of the
          marked glyph.</li>

          <li>Added the current encoding to the font's window title
          (also display a flag to show whether the font has been
          changed)</li>

          <li>When moving points around on an order2 contour
          fontforge could end up with bad control points and would
          then produce annoying internal errors alerting the user
          to this fact.</li>

          <li>The CID Flatten commands did not work when the view
          was compacted.</li>

          <li>CharInfo had been deliberately disabled in CID
          fonts</li>

          <li>Show ATT didn't work with CID keyed fonts</li>

          <li>The preference mapping between mac and opentype small
          caps features was wrong.</li>

          <li>Werner found a strange bug in splinefill that I can't
          reproduce (and can't understand how it could happen) but
          the fix appears obvious.</li>

          <li>Add a command to show what glyphs use the current
          glyph in a substitution (so "A.swash" would show that "A"
          used it, and "i" would show that "fi" used it).</li>

          <li>Changed the extension shown in the Generate Fonts dlg
          for multiple saves to ".pfb". Put in a %s to make it
          obvious that more will be added to the name. Support
          people who want .pfa fonts too.</li>

          <li>The dialog for adding/editing correspondences between
          mac feature/settings and opentype features never went
          away.</li>

          <li>Disable the Default ATT menu if no char is selected
          in the fontview.</li>

          <li>FontForge sometimes had trouble drawing the correct
          rotated glyph in cid fonts on the display lines of the
          fontview.</li>

          <li>Changed the way names used in cidmap files, so there
          are new cidmap files now.</li>

          <li>The ShowAtt dialog could overwrite itself if there
          were enough aats in it. (and at one point the vertical
          scroll bar was set to the bounds of the horizontal scroll
          bar)</li>

          <li>Still getting the windows ascent/descent wrong. This
          time in CID keyed fonts.</li>

          <li>Add some new language translations for things like
          "Bold" (dutch, swedish, norwegian)</li>

          <li>Dragging and dropping a char from the font view into
          the char info dlg (to create a substitution) created a
          crash instead.</li>

          <li>Support more of postscript in the interpreter</li>

          <li>Our svg fonts pointed to a not-yet-existing dtd
          file</li>

          <li>Support for Apple's distortable fonts (sort of like
          truetype multi-master fonts)</li>

          <li>Depressing the control key now makes popups live
          longer (until the mouse moves).</li>

          <li>new command in MM menu: Blend to new font</li>
        </ul>
      </li>

      <li>2-Mar-2004

        <ul>
          <li>Changed name from pfaedit to fontforge</li>
        </ul>
      </li>
    </ul>

    <p>FontForge was first released on 2-Mar-2004. An earlier
    version of the program, called PfaEdit, was begun in Sept of
    2000, released on the web 7-Nov-2000, and moved to
    pfaedit.sf.net on 21-Apr-2001.</p>
  </div>
</body>
</html>