add tooltip with font family to radio selector
remove duplicate css attribute entry; cleanup whitespace
attach font changer only to font radio buttons

The function to set the font family was being attached to all input
elements in the entire document which included the font-size selector.
The result was that changing the font size would strip the font family
class off the body element and replace it with nonsense like
`class="config-font-family-18"`. This meant every time you adjusted the
size, your font pref disappeared and hand to be reset.

Fixes #20
fix broken path to image resource
fix regression in CSS cleanup from 9884e1a

CSSTidy apparently cannot handle vendor specific prefixes in values. It
handles them alright in attributes but choked on values. They apparently
get interpreted as a negative number, the string converted to an int,
and the result is "0". The result was a bogus 1s delay being applied in
lieu of a 3D transition. Webkit opted to apply this to all shape
changes, including window resizes.
run CSSTidy again, this time with proper templates

The template used is in this [gist][tpl] is a much cleaner method than the
previous commit of this (9884e1a) bit it still has a couple issues that
need cleanup:

* chained selectors still need to be moved to their own lines and indented
* IE chokes on valid CSS in @media queries if there is an optional space
* Some browsers choke on unquoted web font format string
* CSSTidy breaks vendor-prefixed values (see 03a09d3)
* OpenType settings need quoting for some browsers

All but the last item can be fixed automatically with this:

	find ./ -iname '*.css' -not -iname '*.min.css' \
	-execdir csstidy {} --silent=true --template=csstidy.tpl --compress_colors=true --compress_font-weight=false --discard_invalid_properties=false --preserve_css=true --remove_bslash=true --sort_properties=true --sort_selectors=true --timestamp=false --merge_selectors=0 --case_properties=1 --optimise_shorthands=0 {} \; \
	-execdir sed '/{$/s/\(\s*\)\([^,]\+\),/\1\2,\n\1/g' -i {} \; \
	-execdir sed '/^@media/s/\(min\|max\)-width\s*\([^ ]\+\)/(\1-width:\2)/' -i {} \; \
	-execdir sed "/src:/s/format(\([^')]\+\))/format(\'\1\')/g" -i {} \; \
	-execdir sed 's/-\(webkit\|moz\|ms\)-\(transition\): 0 / -\1-\2: -\1-transform /g' -i {} \; \
	-execdir vim +StripWhitespace +x {} \;

...using this template for `csstidy.tpl`:

	| {
	|| {
	| | |;
	|}|

	|
	}

	| ||
	|
	|

 [tpl]: https://gist.github.com/alerque/74d6cfc91bfd67a59485
Corrected misspellings.
Merge pull request #38 from alerque/fix-transitions

Fix CSS transitions
Merge pull request #36 from alerque/fix-font-selector

Attach font changer only to font radio buttons
Merge pull request #34 from alerque/config-tooltips

Add tooltip to font family selector in config menu
Merge pull request #41 from zohma/master

29 more misspellings corrected.
Added documentation to node.js generation scripts
fixing hover states.
Make config menu styling more consistent with the rest of the UI. Add colors.css to define UI colors (for future LESS/SASS use)
additional colors
Fix book colors from CSSTidy
remove English strings from language names

Having this string is un-necessary in the case of the default English UI
(if you don't recognize the name of the language, content in that
language is not going to be very useful to you) and outright dead-weight
in the context of a localized UI (if you are using a not-English
version, non-localized strings hard coded in English are not that
useful).

Unless we include a full language name matrix with each language name
localized in each of the languages the site can be localized, it is more
generally useful to just show languages using their localized names (not to
mention easier).

Looking around at major platforms with localization support, this
appears to be the norm now (as opposed to a few years ago when
localization was first rolling out to a few programs and was being
driven by and English-first mindset).

If anything needs a hard-code English fall-back for people to "escape"
from a language they do not understand it would be the name of the
setting and the widget itself. Once they find the widget, having
"English" as a value in the list is enough.
don't display hard coded English strings in index
strip hard coded English strings from text indexes
remove references to obsolete hard coded English localizations