make-tex-bundle.py: munge distribution and date into bundle filename
Add a 'make distrib' rule for making an uploadable distribution

This should be coded with the Git hash instead of just the date, probably,
but keeping it simple for now.
src/type1-font.js: initial clone

This duplicates various bits currently living in font-compiler/, extracting
out only the bits that are necessary for parsing and rendering Type 1 fonts,
as far as I can tell. This is leading up to moving the font compiling into the
master JS file so that we don't need to enumerate and precompile the fonts
that we use.
First part of shipping font data on-the-fly.

The HTML renderer now remembers which fonts the chrome needs and sends the
font data to the chrome on the fly. The chrome will then parse the fonts
itself and render them, rather than requiring pre-compiled fonts. But I
haven't reworked the Type1 font code from pdf.js to fit into my framework.
src/type1-font.js: begin rework

Wrap in a closure for namespacing, remove setting of node.js exports, and
remove the HINTING_ENABLED constant.
src/type1-font.js: get it working

We now have a Type1Font class that uses Mozilla's code to parse the font data
and and general compiled JS functions for rendering on the fly. The structure
is still very awkward since the code hasn't been refactored to fit our
use-case.

The master/chrome/renderer code now needs to load up glyph-encoding.json
before it can render anything. We could also compile the data into the master
-- which increases the coupling between the master JS file and the bundle, but
perhaps I just need to come to grips with the fact that they're going to be
pretty tightly coupled.
src/type1-font.js: strip out unsupported features when compiling characters

I sure hope that we never end up actually needing any of these.
src/type1-font.js: tighten up some more

I think this is about as far as I want to go -- I'd rather have compatibility
with pdf.js's code rather than cleanliness, unless it turns out that this
stuff is a performance bottleneck.
We don't need the font-compiler/ directory anymore.
Use the built-in glyph encoding table in the master.

Ooops, I forgot that I was already including the glyph encoding table! The
master and the bundle are going to be pretty tightly coupled anyway, so I'll
just commit to requiring that.
src/dom-renderer.js: 'className', not 'class', for CSS classes

Which revealed the fact that I was using the wrong vertical-align setting in
the CSS for canvas boxes.
src/type1-font.js: don't chatter for unused glyph names

It turns out that this happens fairly frequently.
test-brockton.html: oops, update for moved files
make-tex-bundle.py: skip various filetypes we won't use

Actually only reduces the bundle size by a little bit, but it helps. The things that
we're skipping are all font-related.
Clean up brockton demo and generate some files for a demo-able release
Add a real ShipTarget base class.

Should've done this a while ago. The plain base class also helpfully functions
as a no-op ship target that does nothing.
src/node-api.js: correct behavior when numIters > 1

The idea here is to only actually invoke the ship target on the final pass.
Otherwise the "chrome" target would output, e.g., 3 copies of the document if
you make 3 passes.
demo/basic/minimalmath.tex: import a painfully simple demo file

AKA the return of latex-minimal.tex. But I'm not planning to keep on editing
this one.
Rework the distribution to be locally runnable.

This means including some demo files and some HTML files that can be run with
a local server. Not fully ready yet since we should include a README and we
don't have a system for actually parsing the brockton.zip file.
Makefile: clarify order and better comments