Simple & minimal Rails application to test the internationalization and localization features of Rails 2.2 and later. I keep this application up-to-date with my current contract, so you can follow the commits for (possible) API changes and gotchas.
It shows how you can override Rails default locale/language ('en') in views, in ActiveRecord validation messages, etc. It shows you how to test internationalization features.
Tries to set some reasonable pattern to load translation files and set locale either from request domain (.com, .de, etc) or request params. Do not ever set locale to cookie or session, as it breaks basic assumptions about web. Read this discussion for context: groups.google.com/group/rails-i18n/browse_thread/thread/de73dbd1309ae640/
The application includes translation file for Czech language so you can easily roll your own Spanish, German, Polish, etc version just by duplicating the file, renaming it and changing the translation strings. After server restart you should see your language in language bar at the top of the page.
Download & unpack archive or git clone from Github [github.com/karmi/rails_i18n_demo_app]
The application requires Rails version 2.2 or later. Either upgrade your Rails gem by running
$ sudo gem update rails
or just download and freeze Rails into vendor/rails
$ rake rails:freeze:edge RELEASE=2.2.2
Run migrations (to be able to test ActiveRecord message localizations) by rake db:migrate
Run script/server and point your browser at localhost:3000
Usually the most sane approach to setting locale/language version of the application is from the domain: application.com loads English, application.es Spanish. This works best for content heavy websites and search engines love it.
The ApplicationController#extract_locale_from_tld sets locale from the top-level domain (ie. the “es” in example.es loads Spanish version). To test this locally, you have to edit your /etc/hosts file by inserting lines like:
127.0.0.1 application.com 127.0.0.1 application.cz