Standardize handling of glyph names for U. F. O. output.

This adds a standards-compliant name mangler and a hash table look-up for glyph names (so that we can iterate names that collide after mangling).

On June 20, 2014 10:28:31 PM Frank Trampe wrote:
> > @@ -0,0 +1,6 @@
> > +[submodule "gnulib"]
> 
> @JoesCat, @jtanx, I'm sort of eager to solve the .gitmodules problem,
> but I don't know much about bootstrap. Does either of you have any
> insight here before I dive in?

Is bootstrap necessary?
When we inherited the new Makefile system in 2012 august, it was unfinished 
and in need of work. Mainly, our existing makefile simply warns of missing 
files, but few people rally know what to do with the warnings anyways. 
Bootstrap doesn't solve much of that anyways, and therefore we simply just 
have to go through configure.ac line-by-line and the large number of 
subdirectories containing Makefile.am and ensure that they all function 
correctly.
I put-off looking at this massive job until about late December of last year 
but did some work on improvement before tagging 20140101

I'd like to avoid .gitincludes and .gitignores since they don't help users 
that aren't using git - and put more focus on the Makefile.am.

The magic is in:
extra_???? to include extra files for install
dist_???? for files that need to be included for distribution but aren't 
explained in the various ??_source ??_include, ......definitions.

To test the dist_??? solution, I've been doing this:
cd ~
cp -pR cleanMaster WorkingCopy
cd ~/WorkingCopy
sh bootstrap    (or older version was "sh autogen.sh")
./configure
make dist
cd ~
md ~/temp
cd ~/temp
tar -xzf ../WorkingCopy/fontforge.tar.gz <-whatever it is called
diff -r ~/temp/fontforge.20140101 ~/CleanMaster

It's a work in progress, but at this point, you should see what you missed.
There is a steep learning curve but it's resolvable.

I still would prefer to finish-up the --without-stuff as practice to tackle 
the big "python" issue that needs resolving for such a long time. This has 
been causing a lot of repeated issues, plus, once this is resolved and 
available to other operating systems such as BSDs, Mac and Windows, it will 
help make it easier for others to access FontForge. The more users that 
have access to it, the better possibility of also having some more 
contributors helping improve FontForge.