Feature #87

Implement localization

Added by yossarian over 3 years ago. Updated over 3 years ago.

Status:Closed Start:
Priority:High Due date:
Assigned to:yossarian % Done:

0%

Category:Layout
Target version:0.4 - Rebel Yell (2b || !2b)
Resolution:

fixed


Description

The site UI needs to be easily localizable into different languages. It seems that the best plugin to make this happen is the Globalize plugin: http://www.globalize-rails.org/globalize/show/Features

A plugin which makes the process easier, through in-place editing of localization files, is available at: http://www.lucaguidi.com/pages/click-to-globalize

History

Updated by yossarian over 3 years ago

  • Status changed from New to Assigned

We've now started implementing localization using the globalize plugin. Don't forget to add the UTF-8 line to the production database.yml file or things are going to mess up on the production box.

Updated by yossarian over 3 years ago

The basic implementation is now complete, at least the infrastructure is there. We still need to do the following:

String replacement

Go through and set up all hard coded strings in templates for internationalization. This is pretty simple. Given a string like:

<p>This is a string in a view in the app</p>

all that's needed is to change it to this:

<p><%= "This is a string in a view in the app".t %></p>

The globalize plugin will do the rest.

Database settings

Ensure that the UTF8 line is in the production database.yml files and that the production databases have been converted to UTF8. See the globalize writeup

Preload translations on production site

It is possible to preload every translated string on application start in production mode. See here.

Route users to the correct language

Set up the app routes so we know which language the request is in.

Updated by yossarian over 3 years ago

For the denmark site which we're primarily worried about at this point, only the string replacements remain, all other stuff is done.

For the london site, we still need to do the database stuff.

Updated by yossarian over 3 years ago

  • Status changed from Assigned to Closed
  • Resolution set to fixed

The london site is now also done. Instances of non-translated stuff probably remain but I'll need to see a list of them before I can go on with getting them all knocked off. I'll close this ticket now and we can get a list going as separate tickets.

Also available in: Atom PDF