GATE ONE HAS NOW BEEN TRANSLATED (probably badly) into: German, Portugeuse, French, Russian, and Spanish.  Thank you Google Translate!  You can set your 'locale' in your 10server.conf.  I still need to make over the JavaScript files though...  Lots are still missing usage of `GateOne.i18n.gettext()`.
setup.py:  Fixed a bug where it wouldn't install correctly unless you ran setup.py from inside the GateOne download/clone dir.
setup.py:  Gate One now uses `entry_points` for discovering plugins.  These entry points get registered by the `setup()` command:  go_plugins, go_applications, and go_<app name>_plugins.  Applications and plugins that wish to integrate into Gate One no longer need to figure out where Gate One is installed and can, in fact, work from within a zip/egg.  I will be moving the 'example' application out of the 'applications' dir and into its own directory with its own setup.py to demonstrate how to use this new functionality.
core/utils.py:  Replaced `get_plugins()` with a new function that uses pkg_resources (from setuptools): `entry_point_files()`.  This will allow for more flexibility/portability with plugins, applications, and application's plugins.  It also means that plugins can be installed outside of Gate One's GATEONE_DIR.
core/utils.py:  Removed `get_applications()` since it is no longer needed with the new `entry_point_files()` function.
core/server.py:  Updated to use the new `entry_point_files()` function.
core/server.py:  Global plugins now use the same plugin.commands format for CLI commands as applications.
core/locale.py:  Locales are now retrieved using the `pkg_resources` module.
Up next:  Getting all the JS, CSS, and theme functions working with pkg_resources...