stub in initial i18n work to match other OpenStack projects

I'd recommend Babel (http://babel.edgewall.org/) since you don't have access to Django's lovely translation machinery. Babel which works well; it's what Nova uses.

The end goal is to generate a root string catalog (usually a .po or .pot file for the en_US language code), which can then be imported into Transifex. Once Transifex knows about your project and its strings, there's a setting to link that resource to a raw file URL on github (still need to try this out to make sure it actually updates...).

TRANSIFEX PROJECT: https://www.transifex.net/projects/p/keystone/

Two last thoughts to keep in the back of your head:

 * Babel can do both internationalization (i18n, translation) and localization (l10n, number/date formats), but for right now I'd say focus on the i18n side. The l10n stuff gets complicated and I think I'll save bringing that up for the next summit.

 * Food for thought: the API needs to support a flag for language code. For example, a dashboard user selects Chinese (zh_CN) as their preferred language, then the dashboard should send along that language code to the API, and the API should respond with the appropriate message string if available.

Gerrit topic: https://review.openstack.org/#q,topic:bp/start-keystone-i18n,n,z

Addressed by: https://review.openstack.org/8833
    setting up babel for i18n work blueprint start-keystone-i18n