Translations files for AlchemyCMS 4.1 and above.
The recommended way of adding Alchemy translations is to download the translation files you need
and save them into your apps config/locales
folder.
Alternatively you could add this gem into your apps Gemfile
, but then you will add all supported translations into the I18n.load_path
which will raise the consumed runtime memory and increase the app start up time.
Download the Javascript translation files you need
and save them into your apps vendor/assets/javascripts/alchemy_i18n
folder.
Require each js locale you need to your vendor/assets/javascripts/alchemy/admin/all.js
file
//= require alchemy_i18n/de
//= require alchemy_i18n/fr
//= require select2_locale_de
//= require select2_locale_fr
//= require flatpickr/de
//= require flatpickr/fr
Or require all js translations at once by adding (not recommended)
//= require alchemy_i18n
This gem only provides translations for Alchemy itself. If you also need translations for ActiveSupport features (like to_sentence
or number_with_currency
, etc.)
you should download the Rails translation files and save them into your apps config/locales
folder.
Alternatively you could add the rails-i18n
gem into your apps Gemfile
, but then you will add all supported translations into the I18n.load_path
which will raise the consumed runtime memory and increase the app start up time.
If you want to use Russian translation and have better i18n support, you should put:
gem 'russian', '~> 0.6.0'
or a gem with similar functionality into your apps Gemfile
.
A ruby translation project managed on Locale that's open to all!
- Edit the translations directly on the AlchemyCMS/alchemy_i18n project on Locale.
- That's it!
- The maintainer will then pull translations from the Locale project and push to Github.
Happy translating!
The gem is available as open source under the terms of the MIT License.