Rails Locale Data Repository
Central point to collect locale data for use in Ruby on Rails.
Add to your Gemfile:
or run this command:
gem install rails-i18n
Note that your rails version must be 3.0 or higher if you want to install
rails-i18n as a gem. For rails 2.x, install it manually as described below.
rails-i18n loads all locale files, pluralization and
transliteration rules available in the gem. This behaviour can be changed, if you
config/environments/* the locales which have to be loaded via
config.i18n.available_locales = ['es-CO', :de]
config.i18n.available_locales = :nl
Download the locale files that are found in the directory rails/locale and put them into the
config/locales directory of your Rails application.
If any translation doesn’t suit well to the requirements of your application, edit them or add your own locale files.
For more information, visit Rails Internationalization (I18n) API on the RailsGuides.
Usage on Rails 2.3
Locale data whose structure is compatible with Rails 2.3 are available on the separate branch rails-2-3.
Available locales are:
ar, az, bg, bn-IN, bs, ca, cs, csb, cy, da, de, de-AT, de-CH, dsb, el, en-AU, en-CA, en-GB, en-IN, en-US, eo, es, es-AR, es-CL, es-CO, es-419, es-MX, es-PE, es-VE, et, eu, fa, fi, fr, fr-CA, fr-CH, fur, gl-ES, gsw-CH, he, hi, hi-IN, hr, hsb, hu, id, is, it, ja, kn, ko, lo, lt, lv, mk, mn, nb, ne, nl, nn, pl, pt-BR, pt-PT, rm, ro, ru, sk, sl, sr, scr, sv-SE, sw, th, tl, tr, uk, uz, vi, wo, zh-CN, zh-TW
Following locales are complete:
az, bg, bs, ca, csb, da, de, de-AT, de-CH, el, en-AU, en-CA, en-GB, en-IN, en-US, eo, es, es-AR, es-CL, es-CO, es-419, es-MX, es-VE, et, eu, fa, fi, fr, fr-CA, fr-CH, fur, gsw-CH, he, hi, hi-IN, hr, hu, is, it, ja, kn, ko, lv, mk, mn, nb, ne nl, pt-BR, pt-PT, ru, sk, sr, scr, sv-SE, sw, th, tl, uk, vi, wo, zh-CN, zh-TW
Following locales have some missing translations or pluralizations:
ar, bn-IN, cs, cy, dsb, es-PE, gl-ES, hsb, id, lo, lt, nn, pl, rm, ro, sl
We always welcome your contributions!
How to contribute
If you are familiar with GitHub operations, follow the procedures described in the subsequent sections.
If you are not,
- Save your locale data on the Gist.
- Open an issue with reference to the Gist you created.
- Get a github account and Git program if you haven’t. See Help.Github for instructions.
svenfuchs/rails-i18nrepository and clone it into your PC.
Create or edit your locale file
- Have a look in
rails/locale/en-US.yml, which can be used as the base of your translation. Note that we use
<<: *errors_messagesto anchor and merge a part of translation data.
- Create or edit your locale file. Please pay attention to save your files as UTF-8.
Test your locale file
Before committing and pushing your changes, test the integrity of your locale file.
Make sure you have included all translations with:
rake i18n-spec:completeness rails/locale/en.yml rails/locale/YOUR_NEW_LOCALE.yml
You can list all complete locales:
Also, you can list all available locales:
Add your locale name to the list in
README.md if it isn’t there.
Send pull request
If you are ready, push the repository into the Github and send us a pull request.
We will do the formality check and publish it as quick as we can.
- i18n-country-translation for translations of country names
- i18n-spec for RSpec matchers to test your locale files
- iso for the list of valid language/region codes and their translations
Tsutomu Kuroda for untiringly taking care of this repository, issues and pull requests