Initial commit of work by James Puckett
♪ Build-scripts and a Rakefile

Now you can compile a font! Works with both FontForge and the Adobe Font
Development Kit for OpenType. The former is what we aim for as our main
compiler, as the latter is closed-source, but to have both is great for
testing the UFO spec.

Run ''rake'' to generate the font. ''rake diagnostics'' will give you an
overview of your current build environment and advise you how to proceed if it
can’t find the right build tools.

If you want more control you can use tools/ufo2otf.py which provides a command
line interface: you can choose input and output files, and which compiler to
use.
This is probably a Unix sin

But I really feel like these extensionless files are a bad idea for usability.
They look odd in Windows explorer, and they break Quicklook on Mac.

An extension ‘txt’ also informs novice users about the role of these files:
they are not programming code, they are primarily meant to be read.
Programatically generate FONTLOG.txt

Via ''rake fontlog''

The FONTLOG is SIL’s concept of a chancelog for a font. When doing a release,
we generate one automatically based on AUTHORS.txt, README.txt and the
repository history.
'rake install' installs the font

Or rather, any otf file found in the folder. I had to remove generating
OpenBaskerville.otf as a dependency, since it can conflict with the upcoming
'generate release' task. I should probably look into rake namespacing.

In the metadata, removed entries related to FOND resources, I am not sure if
they are actually useful, and they could cause conflicts when installing
multiple Open Baskervilles.
'rake release' creates font with generated version number ♫

When a designer uses a font, it is critical that she or he can identify the
particular version unambigously. We also want to make sure that designers can
use our development snapshots. That’s why for every commit there needs to be a
potential version number. We could, theoretically, use git hashes as
identifiers. However, they look cryptic to end users, and they don’t provide
information about the chronology of versions.

Taking cues from the semver.org spec, our version number takes a form X.Y.Z.,
where X is the major version, Y the minor version, and Z the patch version.
Minor versions have a defined set of goals, and get tagged in Git, we started
with 0.0.0 and we are now working towards 0.1.0.

Our patch versions, are built from the source tree after each commit. So from
the first commit after 0.1.0 we can build 0.1.1.

To do a release, we use the ''git describe'' command to tell us the last tag
and the number of commits since that tag, whereupon we base a version number
that we bake into the ufo and thus into the generated font.
'rake package' produces a release package as a zip archive

A build folder is created to put all the assets into before zipping
A white-listing approach is being taken; i.e. files need to be
specifically moved into the build folder before they get zipped.

Both the UFO sources and the generated OTF get marked with the version
number as based on the git

Note there is a pesky bug in this Rakefile:
We use a zip command like

zip -r OpenBaskerville-0.0.56.zip build/OpenBaskerville-0.56

Which produces a zipfile which includes the build folder.
How would one go about to get just the OpenBaskerville-0.0.56
folder in there?

https://github.com/klepas/open-baskerville/issues/10
.gitignore updated for meta-files
more .gitignore love

ignore the build tree
Update author information

Also removed AUTHORS.txt because there was too many
different places to specify AUTHORS
ufo2otf.py takes multiple input files

So next we can let the Rakefile handle multiple ufos

- Note in using argparse I basically broke compatibality
with Python 2.6 (and thus OS X 10.6)
Needs to be fixed -

Also, subtly embedded is the start of webfont generation ( #3 )
We still need to generate css and add ttf2eot though
〠 Rakefile is now project-agnostic 〠

Will automatically search for UFO’s to convert.
Removing AUTHORS.txt broke tools/FONTLOG.py

( and I had forgotten 1 little OpenBaskerville reference
  in the Rakefile )
''rake webfonts'' will generate webfonts ♬
Buildscripts: add backported argparse for Python 2.6 compatibility

https://code.google.com/p/argparse/

> based on the python 2.7 stdlib code, backported to older python versions
> provides argparse for everybody who still needs to support python < 2.7