remove hardcoded "pfaedit" or "fontforge" name in shebang check
manually resolved conflict
Fixed corruption caused by incorrect dumping of named point to SFD file.

Point's name is read by SFDReadUTF7Str(), which requires the name to
be inside double quotes or it will fail, with the added consequence
that any subsequent points in the containing spline to be lost.

Fixed by changing the printf() call to SFDDumpUTF7Str().
Removed unnecessary duplicated calls to GDrawGetUserData.

GDrawGetUserData is called at the beginning of CVPopupSelectInvoked; it isn't necessary to call it again inside every case of the switch.
Merge pull request #1284 from mskala/shebang-simplify

remove hardcoded "pfaedit" or "fontforge" name in shebang check
Merge pull request #1286 from blipvert/fixes/31

Removed unnecessary duplicated calls to GDrawGetUserData.
Merge pull request #1285 from blipvert/fixes/30

Fixed corruption caused by incorrect dumping of named point to SFD file.
Added support for named points in the CharView.

1. Added "Name Point..." item to the Point menu of the Charview.
2. Added "Name Point..." item to the selection popup menu for a point.
3. Show point names in CharView, similar to what is done for contours.
4. Added an icon to the tango theme, with a placeholder for the 2012 theme.
Merge pull request #1287 from blipvert/fixes/32

Added support for named points in the CharView.
Hinting, OTF, autohinting.

There are a few places where rounding occurs. When loading an OpenType
the hint rectangles applyed by FontForge are done inside the
SCGuessHintInstancesLight() function. When saving to OpenType there is
a chance that hint->width has had a slight rounding error applied, as
such it is not *exactly* 20 or 21 and thus the upper and lower hint is
not applied. And finally, what might be the root of it, inside the
Autohint code there is at times a slight rounding error which might
cause 20 to be 19.9999 for example. So I've added some stuff to the
autohint code to clamp to 21 or 20 if the values are very close. It is
probably best to do that there rather than special case close values
in other parts of the code. Though perhaps loading from opentype needs
some help there still so that there is some tolerence to loading
opentypes with slight rounding errors in them. So those hints can be
resurrected and then improved and saved.

Still need to cleanup, this is a dirty commit with bunches of crap in there
for debugging etc.
cleaned it up, ran into a strange bug with float truncation when I tried
to move some of the clamp() utilitiy function to gutils/ffnumeric.c/h
Merge pull request #1289 from monkeyiq/2014mar/otf-hint-v1

2014mar/otf hint v1