Don't print strippedname. Fixes #1829. Related: #1743
Merge pull request #1830 from jtanx/strippedname

Don't print strippedname. Fixes #1829. Related: #1743
Allow a U. F. O. to omit fontinfo.plist.
Fix #1779 Native script tests never 'fail'

Change 66ff553a6f2044d382a0f78702886efe625a8fa6 wanted to allow interactive
executions to continue in spite of errors encountered in native scripts.
It set up the setjmp/longjmp information that `traceback()` could use to
return to the native script statement execution loop.

Unfortunately while other parts of that and other changes were well
directed towards the object interactive mode, the `setjmp()` would run
in all modes.  This caused *any* `Error()` or other exception to always
return to the statement loop.  And that routine ended in an `exit(0)`,
forcing every native script execution to return a zero exit code.

This change simply makes the`setjmp()` also conditional on the interactive
flag.  With this change `Quit(N)` sets exit code N, `Error()` displays the
error message and then set exit code 1, and exceptions also display errors
and then set exit code 1.

Tested with `Quit()`, `Error()` and exceptions, in both main programs and
in subroutines.

Also see further descriptions in issue #1779.
Fix .pe tests to use relative paths and command-line args
Moving FontforgeInternal

Having a directory inside the bin is generally frowned upon, and causes
issues with Homebrew due to our audit red-flagging that behaviour. This
(theoretically) changes that by moving that internal directory to
libexec/bin. This should work okay, theoretically. Let me know what you
all think.
Don't try to download mingliu

It's not legal, and the copy we were downloading was corrupt anyway

Disable autohinting test122.pe for now, it fails, and no-one has come up
with a quick fix.
View/Combinations/KernPairs mistakenly right-to-left

Issue #1811 mentioned trying to understand kern pairs by consulting the
View / Combinations / Kern Pairs UI dialog, in addition to the other
dialogs that can display kern pairs.  While tracing reporters steps with
their cited TTF I noticed something odd.  For just 'some' kern pairs,
the character pair would be displayed in reversed order and
right-justified.  Very much as though FF thought right-to-left display
was required.

I verified this behavior with the ./tests/fonts/Caliban.sfd file, where
for example 'sometimes' "Lv" would be displayed right-justified as "vL",
"Fo" would be "oF", etc.  This would happen for a small random assortment
of character pairs.

Disabling setting of the `r2l` flag within `fontforgeexe/combinations.c`
routine `CheckLeftRight()` did not stop the problem, as breakpoints on
the right-to-left display code in `KP_ExposeKerns()` found some pairs
had the flag set anyway.

Checking further found that when the `r2l` flag was added in 2002, no
additional initialization code was put into `KPBuildKernList()` or
`void KPBuildAnchorList()`.  Uninitialized allocated memory would
occasionally 'set' the flag `r2l`.

This change uses `calloc()` vs. `malloc()`, and has `CheckLeftRight()`
always set the flag to either true or false.  This guarantees flag is
defaulted to false, and is left set correctly on each call.

Tested before and after against the Caliban.sfd file.  All pairs now
consistently displayed correctly.
Pretty message on TTC open with missing/bad font names

Very minor change to make font selection a bit more understandable,
when opening a TTC file where some/all font names in the TTC are
missing or bad.  User is slightly reassured to see there are multiple
separate fonts within the TTC.

For each missing font name, a line of "Unknown font name NN" is
substituted in the list presented by the dialog "There are multiple
fonts in this file, pick one".  If user want to examine them one by
one they are at least assured they are picking different fonts.

Tested against broken downloaded font /tests/fonts/mingliu.ttc and
against the correct mingliy.ttc file from Windows.
Allocate user_data for the point information window for Spiro since the window destructor likes to free it. Also eliminate the duplicate call to the window destructor at the end of SpiroPointGetInfo since the event loop handles that.
Merge pull request #1842 from fontforge/spiro_point_info_crash_1

Avoid crashes when closing the point info window in Spiro mode.
Merge pull request #1841 from tshinnic/1820_ttf_short_crash_2

Pretty message on TTC open with missing/bad font names
Merge pull request #1840 from tshinnic/view_combin_kern_pair_1

View/Combinations/KernPairs mistakenly right-to-left
Merge pull request #1833 from fontforge/ufo_optional_fontinfo_1

Allow a U. F. O. to omit fontinfo.plist.
Merge pull request #1834 from rrthomas/master

Allow native test scripts to return status, and fix so they work (redo PR #1780 to fix issue #1779)
Merge pull request #1838 from DomT4/internalpatch

Moving FontforgeInternal
A few changes to update the PR for changing the location of the
FontForgeInternal directory.

https://github.com/fontforge/fontforge/pull/1838
meta-T on the path max
Rearrange check for blank tooltips

As reported in #1807, for many tooltips, single line tooltips were blank
and the last line of multi-line tooltips were blank.

In an attempt to curb empty tooltips, a change misinterpreted how a
character count was being used.  The value was actually trying to flag
leading lines of a multi-line tooltips.

This change makes that leading/last line flagging a tiny bit more
explicit, adding comments.

Trying to implement the original desire to omit tooltips with empty texts,
this change alters when the loop checks for end-of-string. (do-while
changed to while)  Also, a much earlier check for empty string will
simply exit and not display an empty tooltip text.

In addition to testing normal tooltips (easiest check is hovering over
the checkbox labels in the Generate Fonts dialog; these show two line,
single line, and 11 line tooltips), a series of empty and partially
empty texts were exercised.
```
fontforgeexe/savefontdlg.c
  2611         gcd[k].gd.popup_msg = (unichar_t *) _("Check the glyph outlines for standard errors before saving\nThis can be slow.");

      popup_msg = _("Check the glyph outlines for standard errors before saving\n");
  Shows as correct first line, but then no second line at all - a
    one line tooltip.
  Did GDrawWindowFontMetrics() determine line height to be only one?

      popup_msg = _("\nThis can be slow.");
  Shows as first line blank, second line "This can be slow."

      popup_msg = _("\n");
  A one character blank tooltip is displayed.
    Well, a "\n" sure does say "give me a blank line", so displaying
    *something* seems the correct thing to do.

      popup_msg = _("");
  Nothing is displayed.
```
These special conditions seem to give reasonable results.

This change should close #1807
Merge pull request #1854 from monkeyiq/2014oct/ffidir-fixup1

A few changes to update the PR for changing the location of the FontForgeInternal directory.