convert MAC to UNIX style line endings on json files
remove commented out css blocks that have been obsoleted

I left some blocks that I could not identify or that looked like options
that could still prove useful, but all the commented CSS code that I
could verify had been obsoleted either by removal of the relevant DOM
nodes or by implementing the styles elsewhere in the CSS or simply not
did not produce a better result I ripped out.
normalize whitespace in CSS files

If there was a rhyme or reason to the indent levels is the CSS files I
couldn't make out what it was. It looks like it might have been leftover
from a templating system or nested structure.

Otherwise this just normalizes coding style to remove the single-line
entries that are a pain to edit, esp in an editor with line-wrap turned
off.

Some more cleanup could be done to properly comment sections and fix the
inconsistent breaking between related and unrelated items.
remove obsolete webfont formats, leave only WOFF

The switch to jQuery 2 already rules out all of the browsers that would
be picked up by the alternate font formats. EOT is only needed for IE8,
but 9 is required for jQuery 2. The TTF and SVG formats only picked up
older mobile platforms, but all the ones supported by jQuery (and even
2 versions older) support WOFF.
run all project CSS through csstidy

The inconsistent code styling and attribute order was making my head hurt
looking for where things were set and it was too much to rewrite by hand. I
ended up running everything through css tidy to normalize the order of
properties and selectors, whitespace, value styles, etc. I opted not to have
it optimize for shorthand values,  merge duplicates, or any other options I
thought would make it less readable.

Since the output of csstidy is not indented, I tweaked the output to use
one selector per line and re-indented the whole thing using vim's syntax
plugin. Here is a quick vim script to duplicate the same results:

    :%!csstidy % --silent=true --preserve_css=true --sort_selectors=1 --merge_selectors=0 --compress_font-weight=false
    :%!sed '/{$/s/,/,\n/g'
    :%s/: */: /g
    :norm gg=G

Note vim's indenting has issues after some kinds of comment blocks. The
output was manually tweaked to correct that.
remove CSS attributes bogusly commented with prefix
fix fall-back on custom font declaration

Both ways work in the end, but the fall-back happening here is not from one
font family to another but from a possible local installation of the same font
to using a webfont version from the app. The CSS handling this fall-back
should be the font-face declaration, not the family selector.
Merge pull request #29 from alerque/misc-fixes

Cleanup CSS coding style and remove obsolete bits