<commit_before>h2. Internationalization (i18n)

This guide covers how Spree uses Rails' internationalization features, and how you can leverage and extend these features in your Spree contributions and extensions. After reading it, you should be familiar with:

* How Spree is internationalized
* How to add translations
* Internationalizing extensions
* Disabling internationalization

endprologue.

h3. How Spree i18n works

Spree uses the standard Rails approach to internationalization so we suggest take some time to review the "official Rails i18n guide":http://guides.rubyonrails.org/i18n.html and the "rails-i18n.org wiki":http://rails-i18n.org/wiki to help you get started.

h4. The spree-i18n project

Spree now stores all of the translation information in a separate Github project known as "spree_i18n":http://github.com/spree/spree_i18n.  This is a stand alone project with a large number of volunteer committers who maintain the locale files.  This is basically the same approach
followed by the Rails project which keeps their localizations in "rails-i18n":http://github.com/svenfuchs/i18n.
<commit_msg>Correct name of spree_i18n project<commit_after>h2. Internationalization (i18n)

This guide covers how Spree uses Rails' internationalization features, and how you can leverage and extend these features in your Spree contributions and extensions. After reading it, you should be familiar with:

* How Spree is internationalized
* How to add translations
* Internationalizing extensions
* Disabling internationalization

endprologue.

h3. How Spree i18n works

Spree uses the standard Rails approach to internationalization so we suggest take some time to review the "official Rails i18n guide":http://guides.rubyonrails.org/i18n.html and the "rails-i18n.org wiki":http://rails-i18n.org/wiki to help you get started.

h4. The spree_i18n project

Spree now stores all of the translation information in a separate Github project known as "spree_i18n":http://github.com/spree/spree_i18n.  This is a stand alone project with a large number of volunteer committers who maintain the locale files.  This is basically the same approach
followed by the Rails project which keeps their localizations in "rails-i18n":http://github.com/svenfuchs/i18n.

{'fraction_non_alphanumeric': 0.05538325210456358, 'fraction_numerical': 0.02303943287549845, 'mean_word_length': 5.037433155080214, 'pattern_counts': {'":': 8, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '5540076', 'n_tokens_mistral': 658, 'n_tokens_neox': 607, 'n_words': 280}