Mark strings in JST views for translation
Move TRANSLATE comment outside tag in JST
Mark translation strings in viewer
Incorrectly Marked string;  Comes from DB
Replace translation strings with _.t function
Insert tiny translation library into viewer load
Translations via google translate

Spanish, French, Simplified Chinese, & German

The aliases file is incomplete and is only used force en-us to show
incorrect languages for testing
Tiny translation library

This is the simplest possible thing that will work for translating the
viewer.  Simple key->value lookups for languages, no pluralization or
fancy shenanigans.

Needs a bit more code cleanup, but is working
Rename sample translations to use 639-3 codes
Pass document's language to i18n lib

Right now we'll base the viewer's ui language off it
load translations via jsonp

And redraw viewer after load
Speeling.  language not langauge
Moved translations endpoint to under resources
Call viewer.open('InitalLoad') in order to redraw

Not sure of the advisability of this.  Will be obsoleted with next-gen
viewer anyway.
Rename Anno to Note

Same number of chars but meaning is more clear
Missed AnnoBy
Rework JST templates to use new translation format

Strings are now underscore instead of CamelCase, support
pluralization rules, and are driven by a shared yaml file stored in documentcloud
Upgrade viewer to new i18n lib

Uses common translation tables that originate in main app.
Widen "Save as Draft" button on annotation
Updated version of i18n lib

Somehow the branch had an old copy.  It should use the same copy as the
workspace for api fidelity between the two, and so they can share packs.