Devise "is a flexible authentication solution for Rails based on Warden". Internationalization (aka i18n) is a "means of adapting computer software to different languages, regional differences and technical requirements of a target market".
Devise supports i18n in controllers, models, and in other areas, but it does not have support for internationalized views. devise-i18n adds this support. Devise also does not include the actual translations. devise-i18n does this too.
devise-18n is for devise v2 and later. For devise v1.5, use the devise-1.5 branch.
Add to your Gemfile:
Assuming you have not previously generated Devise's views into your project, that's all you need to do. If you have previously done this, you will need to regenerate your views (see the next section) and then reapply whatever customizations that made you do this in the first place.
NOTE: If you have the
simple_form gem in your Gemfile, this command will generate the corresponding views using the simple_form form builder.
devise:i18n:views generator will copy all devise-i18n's views to your application so that you can modify the files as you wish.
rails g devise:i18n:views
You should only do this if you really need to, though, because doing this will make it so that you won't get the updated views should they change in a future version of devise-i18n. To "uncustomize" the views, just delete them, and your app will go back to grabbing devise-i18n's default views.
If, for whatever reason, you want to change devise-i18n's translations, you can generate the locale file into your project with
rails g devise:i18n:locale it
which will generate
config/locales/devise.views.it.yml. If you're doing this to add a missing translation or to improve an existing one, it'd be nice if you could share your suggestions with us!
Contributing translations to devise-i18n
Edit the translations directly on the devise-i18n project on Locale. That's it! The maintainer will periodically pull translations from the Locale project and push to Github.
Alternately, you can create a pull request on GitHub.
In general, the tone of translations should be friendly, polite, and succinct. Certain languages (including Japanese and Korean) should use a more formal tone which is the standard for customer messages in those languages.
Copyright (c) 2011 Christopher Dell. See LICENSE.txt for further details.