Globalize for Rails 1.2 released!

The Globalize’s developer team is happy to annouce the official release of Globalize for Rails 1.2

Besides being compatible with the latest shiny & jaw-dropping Ruby on Rails 1.2 release this Globalize release adds two new major features:

For a smooth upgrade please note that a minor change to the database schema is required.

NOTE: If you install the plugin via script/plugin install, then your schema will be automatically updated (default rails environment).

You can also accomplish this by running the included Rake task:

rake globalize:upgrade_schema_to_1_dot_2

(This in fact doesn’t do anything more than add a string column ‘namespace’ to the table globalize_translations, so you could do that manually, too.)

Posted on 01 Mar 2007

Overview for busy people

Globalize implements three basic types of translation:

  1. Dates, currencies, etc: language dependent, but also (often) country/locale dependent. This feature provides convenient methods for relevant data types. 12345.67.localize12.345,67
  2. Content in the database, for specific fields in specific tables: once the translates method is added to the relevant model, the fields indicated with that method call gain the ability to have translated content sitting in the database. An operator (possibly the developer) will need to add these translated texts.
  3. Arbitrary strings: any string that you would like, with added flexiblity for including parameters (for example: ‘one’ in the singular form of a phrase and an actual number for the plural form)

Using these three mechanisms, all user-facing content ought to be translatable.

For a quick overview of Globalize usage see: How to use. For more walkthroughs, articles and howtos see: Documentation

Screencast(s)

We’d like to publish a screencast here – or better yet, a short screencast for each of several aspects of using Globalize.

If you’re volunteering for this, please contact us.

revision 1 · 03.06.09 09:25 · by: Marko Seppä