Managing translations (i18n)

Whenever someone adds a new translation key to Decidim, Crowdin gets notified and the new content is available to be translated from Crowdin’s Decidim dashboard.

When a translator translates any key from Crowdin, it automatically creates a PR in Github, adding the keys in the corresponding yaml files.

🌈

Setup the new language in Crowdin’s Decidim project (or open an issue on Github asking an admin to do that).

Add the locale mapping in the crowdin.yml file

Translate at least one key from every engine, so, your yaml files are not empty. The easiest way to do this is to automatically translate and sync all the content. Later you’ll be able to fix the content that wasn’t properly translated.

Add Foundation Datepicker's translations (PR).

Add the new language to available_locales (PR).

Add the language in decidim-core/spec/lib/available_locales_spec.rb.

Generate the development app and cd into it.

Change the config/initializer/decidim.rb file and add your locale to Decidim.available_locales.

rake db:drop db:setup to drop, create, load schema and seed the DB.