okfn/openspending — Issue #379: Work out internationalization in the front-end
Author: pudo
Created: 2012-01-22 12:28:33+00:00
State: open
Labels: documentation, feature

We have a lot of people who're offering to do translations but the software-side support for this is broken. Need to work out the following:

* Get a listing of available languages (by interacting with the translation mechanism and not as a hard-coded array) and display that in the interface (e.g. Bootstrap modal dialog). Validate that the ``/locale`` switch really works.
* Review content language auto-negotation.
* Consider if the specified dataset language of c.dataset can be used as a mechanism for content language detection (i.e. Italian datasets are biased towards using italian in the UI). This is made difficult by multi-language datasets.
* Document the full workflow for developers to update the l10n files.
* Go through the controller sources and eliminate non-gettexted strings.

When this is done, notify @lucychambers to coordinate a translation push.