Regenerate guides

2 files changed, 293 insertions, 46 deletions

diff --git a/railties/doc/guides/html/form_helpers.html b/railties/doc/guides/html/form_helpers.html
index 6169574d35..54155cddb6 100644
--- a/railties/doc/guides/html/form_helpers.html
+++ b/railties/doc/guides/html/form_helpers.html
@@ -90,6 +90,15 @@
             
               <li><a href="#_dealing_with_ajax">Dealing with Ajax</a></li>
             
+            </ul>
+          </li>
+          <li>
+          <a href="#_customising_form_builders">Customising Form Builders</a>
+          </li>
+          <li>
+          <a href="#_understanding_parameter_naming_conventions">Understanding Parameter Naming Conventions</a>
+            <ul>
+            
               <li><a href="#_basic_structures">Basic structures</a></li>
             
               <li><a href="#_combining_them">Combining them</a></li>
@@ -738,45 +747,44 @@ http://www.gnu.org/software/src-highlite -->
 </div>

 <h3 id="_dealing_with_ajax">5.2. Dealing with Ajax</h3>

 <div class="paragraph"><p>Unlike other forms making an asynchronous file upload form is not as simple as replacing <tt>form_for</tt> with <tt>remote_form_for</tt>. With an AJAX form the serialization is done by javascript running inside the browser and since javascript cannot read files from your hard drive the file cannot be uploaded. The most common workaround is to use an invisible iframe that serves as the target for the form submission.</p></div>

-<div class="paragraph"><p>Customising Form Builders</p></div>

+</div>

+<h2 id="_customising_form_builders">6. Customising Form Builders</h2>

+<div class="sectionbody">

+<div class="paragraph"><p>As mentioned previously the object yielded by <tt>form_for</tt> and <tt>fields_for</tt> is an instance of FormBuilder (or a subclass thereof). Form builders encapsulate the notion of displaying a form elements for a single object. While you can of course write helpers for your forms in the usual way you can also subclass FormBuilder and add the helpers there. For example</p></div>

 <div class="listingblock">

 <div class="content">

-<pre><tt>As mentioned previously the object yielded by `form_for` and `fields_for` is an instance of FormBuilder (or a subclass thereof). Form builders encapsulate the notion of displaying a form elements for a single object. While you can of course write helpers for your forms in the usual way you can also subclass FormBuilder and add the helpers there. For example</tt></pre>

-</div></div>

-<div class="paragraph"><p>&lt;% form_for @person  do |f| %&gt;

+<pre><tt>&lt;% form_for @person  do |f| %&gt;

   &lt;%= text_field_with_label f, :first_name %&gt;

-&lt;% end %&gt;</p></div>

-<div class="listingblock">

-<div class="content">

-<pre><tt>can be replaced with</tt></pre>

+&lt;% end %&gt;</tt></pre>

 </div></div>

-<div class="paragraph"><p>&lt;% form_for @person, :builder =&gt; LabellingFormBuilder do |f| %&gt;

-  &lt;%= f.text_field :first_name %&gt;

-&lt;% end %&gt;</p></div>

+<div class="paragraph"><p>can be replaced with</p></div>

 <div class="listingblock">

 <div class="content">

-<pre><tt>by defining a LabellingFormBuilder class similar to the following:

-

-[source, ruby]</tt></pre>

+<pre><tt>&lt;% form_for @person, :builder =&gt; LabellingFormBuilder do |f| %&gt;

+  &lt;%= f.text_field :first_name %&gt;

+&lt;% end %&gt;</tt></pre>

 </div></div>

-<div class="paragraph"><p>class LabellingFormBuilder &lt; FormBuilder

-  def text_field attribute, options={}

-    label(attribute) + text_field(attribute, options)

-  end

-end</p></div>

+<div class="paragraph"><p>by defining a LabellingFormBuilder class similar to the following:</p></div>

 <div class="listingblock">

-<div class="content">

-<pre><tt>If you reuse this frequently you could define a `labeled_form_for` helper that automatically applies the `:builder =&gt; LabellingFormBuilder` option.

-

-The form builder used also determines what happens when you do</tt></pre>

-</div></div>

-<div class="paragraph"><p>&lt;%= render :partial =&gt; f %&gt;</p></div>

+<div class="content"><!-- Generator: GNU source-highlight 2.9

+by Lorenzo Bettini

+http://www.lorenzobettini.it

+http://www.gnu.org/software/src-highlite -->

+<pre><tt><span style="font-weight: bold"><span style="color: #0000FF">class</span></span> LabellingFormBuilder <span style="color: #990000">&lt;</span> FormBuilder

+  <span style="font-weight: bold"><span style="color: #0000FF">def</span></span> text_field attribute<span style="color: #990000">,</span> options<span style="color: #990000">=</span><span style="color: #FF0000">{}</span>

+    label<span style="color: #990000">(</span>attribute<span style="color: #990000">)</span> <span style="color: #990000">+</span> text_field<span style="color: #990000">(</span>attribute<span style="color: #990000">,</span> options<span style="color: #990000">)</span>

+  <span style="font-weight: bold"><span style="color: #0000FF">end</span></span>

+<span style="font-weight: bold"><span style="color: #0000FF">end</span></span></tt></pre></div></div>

+<div class="paragraph"><p>If you reuse this frequently you could define a <tt>labeled_form_for</tt> helper that automatically applies the <tt>:builder =&gt; LabellingFormBuilder</tt> option.</p></div>

+<div class="paragraph"><p>The form builder used also determines what happens when you do</p></div>

 <div class="listingblock">

 <div class="content">

-<pre><tt>If `f` is an instance of FormBuilder then this will render the 'form' partial, setting the partial's object to the form builder. If the form builder is of class LabellingFormBuilder then the 'labelling_form' partial would be rendered instead.

-

-Understanding Parameter Naming Conventions</tt></pre>

+<pre><tt>&lt;%= render :partial =&gt; f %&gt;</tt></pre>

 </div></div>

+<div class="paragraph"><p>If <tt>f</tt> is an instance of FormBuilder then this will render the <em>form</em> partial, setting the partial&#8217;s object to the form builder. If the form builder is of class LabellingFormBuilder then the <em>labelling_form</em> partial would be rendered instead.</p></div>

+</div>

+<h2 id="_understanding_parameter_naming_conventions">7. Understanding Parameter Naming Conventions</h2>

+<div class="sectionbody">

 <div class="paragraph" id="parameter_names"><p>As you&#8217;ve seen in the previous sections, values from forms can appear either at the top level of the params hash or may appear nested in another hash. For example in a standard create

 action for a Person model, <tt>params[:model]</tt> would usually be a hash of all the attributes for the person to create. The params hash can also contain arrays, arrays of hashes and so on.</p></div>

 <div class="paragraph"><p>Fundamentally HTML forms don&#8217;t know about any sort of structured data, all they generate is name-value pairs. The arrays and hashes you see in your application are the result of some parameter naming conventions that Rails uses.</p></div>

@@ -795,7 +803,7 @@ action for a Person model, <tt>params[:model]</tt> would usually be a hash of al
 </td>

 </tr></table>

 </div>

-<h3 id="_basic_structures">5.3. Basic structures</h3>

+<h3 id="_basic_structures">7.1. Basic structures</h3>

 <div class="paragraph"><p>The two basic structures are arrays and hashes. Hashes mirror the syntax used for accessing the value in the params. For example if a form contains</p></div>

 <div class="listingblock">

 <div class="content">

@@ -829,7 +837,7 @@ http://www.gnu.org/software/src-highlite -->
 &lt;input name="person[phone_number][]" type="text"/&gt;</tt></pre>

 </div></div>

 <div class="paragraph"><p>This would result in <tt>params[:person][:phone_number]</tt> being an array.</p></div>

-<h3 id="_combining_them">5.4. Combining them</h3>

+<h3 id="_combining_them">7.2. Combining them</h3>

 <div class="paragraph"><p>We can mix and match these two concepts. For example, one element of a hash might be an array as in the previous example, or you can have an array of hashes. For example a form might let you create any number of addresses by repeating the following form fragment</p></div>

 <div class="listingblock">

 <div class="content">

@@ -847,7 +855,7 @@ http://www.gnu.org/software/src-highlite -->
 <td class="content">Array parameters do not play well with the <tt>check_box</tt> helper. According to the HTML specification unchecked checkboxes submit no value. However it is often convenient for a checkbox to always submit a value. The <tt>check_box</tt> helper fakes this by creating a second hidden input with the same name. If the checkbox is unchecked only the hidden input is submitted. If the checkbox is checked then both are submitted but the value submitted by the checkbox takes precedence. When working with array parameters this duplicate submission will confuse Rails since duplicate input names are how it decides when to start a new hash. It is preferable to either use <tt>check_box_tag</tt> or to use hashes instead of arrays.</td>

 </tr></table>

 </div>

-<h3 id="_using_form_helpers">5.5. Using form helpers</h3>

+<h3 id="_using_form_helpers">7.3. Using form helpers</h3>

 <div class="paragraph"><p>The previous sections did not use the Rails form helpers at all. While you can craft the input names yourself and pass them directly to helpers such as <tt>text_field_tag</tt> Rails also provides higher level support. The two tools at your disposal here are the name parameter to <tt>form_for</tt>/<tt>fields_for</tt> and the <tt>:index</tt> option.</p></div>

 <div class="paragraph"><p>You might want to render a form with a set of edit fields for each of a person&#8217;s addresses. Something a little like this will do the trick</p></div>

 <div class="listingblock">

@@ -900,7 +908,7 @@ http://www.gnu.org/software/src-highlite -->
 </div></div>

 <div class="paragraph"><p>produces exactly the same output as the previous example.</p></div>

 </div>

-<h2 id="_building_complex_forms">6. Building Complex forms</h2>

+<h2 id="_building_complex_forms">8. Building Complex forms</h2>

 <div class="sectionbody">

 <div class="paragraph"><p>Many apps grow beyond simple forms editing a single object. For example when creating a Person instance you might want to allow the user to (on the same form) create multiple address records (home, work etc.). When later editing that person the user should be able to add, remove or amend addresses as necessary. While this guide has shown you all the pieces necessary to handle this, Rails does not yet have a standard end-to-end way of accomplishing this, but many have come up with viable approaches. These include:</p></div>

 <div class="ulist"><ul>

@@ -931,7 +939,7 @@ James Golick&#8217;s <a href="http://github.com/giraffesoft/attribute_fu/tree">a
 </li>

 </ul></div>

 </div>

-<h2 id="_changelog">7. Changelog</h2>

+<h2 id="_changelog">9. Changelog</h2>

 <div class="sectionbody">

 <div class="paragraph"><p><a href="http://rails.lighthouseapp.com/projects/16213-rails-guides/tickets/1">Lighthouse ticket</a></p></div>

 <div class="ulist"><div class="title">Authors</div><ul>

diff --git a/railties/doc/guides/html/i18n.html b/railties/doc/guides/html/i18n.html
index cc100e2171..47a9abb93c 100644
--- a/railties/doc/guides/html/i18n.html
+++ b/railties/doc/guides/html/i18n.html
@@ -50,6 +50,10 @@
             
               <li><a href="#_setting_and_passing_the_locale">Setting and passing the locale</a></li>
             
+              <li><a href="#_setting_locale_from_the_domain_name">Setting locale from the domain name</a></li>
+            
+              <li><a href="#_setting_locale_from_the_url_params">Setting locale from the URL params</a></li>
+            
             </ul>
           </li>
           <li>
@@ -82,7 +86,7 @@
             
               <li><a href="#_translations_for_activerecord_models">Translations for ActiveRecord models</a></li>
             
-              <li><a href="#_other_translations_and_localizations">Other translations and localizations</a></li>
+              <li><a href="#_overview_of_other_built_in_methods_that_provide_i18n_support">Overview of other built-in methods that provide I18n support</a></li>
             
             </ul>
           </li>
@@ -97,9 +101,18 @@
             </ul>
           </li>
           <li>
+          <a href="#_conclusion">Conclusion</a>
+          </li>
+          <li>
+          <a href="#_contributing_to_rails_i18n">Contributing to Rails I18n</a>
+          </li>
+          <li>
           <a href="#_resources">Resources</a>
           </li>
           <li>
+          <a href="#_authors">Authors</a>
+          </li>
+          <li>
           <a href="#_footnotes">Footnotes</a>
           </li>
           <li>
@@ -244,8 +257,17 @@ I18n<span style="color: #990000">.</span>load_path <span style="color: #990000">
 <span style="font-style: italic"><span style="color: #9A1900"># set default locale to something else then :en</span></span>

 I18n<span style="color: #990000">.</span>default_locale <span style="color: #990000">=</span> <span style="color: #990000">:</span>pt</tt></pre></div></div>

 <h3 id="_setting_and_passing_the_locale">2.3. Setting and passing the locale</h3>

-<div class="paragraph"><p>By default the I18n library will use :en (English) as a I18n.default_locale for looking up translations (if you do not specify a locale for a lookup).</p></div>

-<div class="paragraph"><p>If you want to translate your Rails application to a single language other than English you can set I18n.default_locale to your locale. If you want to change the locale on a per-request basis though you can set it in a before_filter on the ApplicationController like this:</p></div>

+<div class="paragraph"><p>If you want to translate your Rails application to a <strong>single language other than English</strong> (the default locale), you can set I18n.default_locale to your locale in <tt>environment.rb</tt> or an initializer as shown above, and it will persist through the requests.</p></div>

+<div class="paragraph"><p>However, you would probably like to <strong>provide support for more locales</strong> in your application. In such case, you need to set and pass the locale between requests.</p></div>

+<div class="admonitionblock">

+<table><tr>

+<td class="icon">

+<img src="./images/icons/warning.png" alt="Warning" />

+</td>

+<td class="content">You may be tempted to store choosed locale in a <em>session</em> or a <em>cookie</em>. <strong>Do not do so</strong>. The locale should be transparent and a part of the URL. This way you don&#8217;t break people&#8217;s basic assumptions about the web itself: if you send a URL of some page to a friend, she should see the same page, same content. A fancy word for this would be that you&#8217;re being <a href="http://en.wikipedia.org/wiki/Representational_State_Transfer"><em>RESTful</em></a>. There may be some exceptions to this rule, which are discussed below.</td>

+</tr></table>

+</div>

+<div class="paragraph"><p>The <em>setting part</em> is easy. You can set locale in a <tt>before_filter</tt> in the ApplicationController like this:</p></div>

 <div class="listingblock">

 <div class="content"><!-- Generator: GNU source-highlight 2.9

 by Lorenzo Bettini

@@ -253,16 +275,131 @@ http://www.lorenzobettini.it
 http://www.gnu.org/software/src-highlite -->

 <pre><tt>before_filter <span style="color: #990000">:</span>set_locale

 <span style="font-weight: bold"><span style="color: #0000FF">def</span></span> set_locale

-  <span style="font-style: italic"><span style="color: #9A1900"># if this is nil then I18n.default_locale will be used</span></span>

+  <span style="font-style: italic"><span style="color: #9A1900"># if params[:locale] is nil then I18n.default_locale will be used</span></span>

   I18n<span style="color: #990000">.</span>locale <span style="color: #990000">=</span> params<span style="color: #990000">[:</span>locale<span style="color: #990000">]</span>

 <span style="font-weight: bold"><span style="color: #0000FF">end</span></span></tt></pre></div></div>

-<div class="paragraph"><p>This will already work for URLs where you pass the locale as a query parameter as in example.com?locale=pt (which is what Google also does).</p></div>

+<div class="paragraph"><p>This requires you to pass the locale as a URL query parameter as in <tt>http://example.com/books?locale=pt</tt>. (This is eg. Google&#8217;s approach). So <tt>http://localhost:3000?locale=pt</tt> will load the Portugese localization, whereas <tt>http://localhost:3000?locale=de</tt> would load the German localization, and so on.</p></div>

+<div class="paragraph"><p>Of course, you probably don&#8217;t want to manually include locale in every URL all over your application, or want the URLs look differently, eg. the usual <tt>http://example.com/pt/books</tt> versus <tt>http://example.com/en/books</tt>. Let&#8217;s discuss the different options you have.</p></div>

+<div class="admonitionblock">

+<table><tr>

+<td class="icon">

+<img src="./images/icons/important.png" alt="Important" />

+</td>

+<td class="content">Following examples rely on having locales loaded into your application available as an array of strings like <tt>["en", "es", "gr"]</tt>. This is not inclued in current version of Rails 2.2&#8201;&#8212;&#8201;forthcoming Rails version 2.3 will contain easy accesor <tt>available_locales</tt>. (See <a href="http://github.com/svenfuchs/i18n/commit/411f8fe7">this commit</a> and background at <a href="http://rails-i18n.org/wiki/pages/i18n-available_locales">Rails I18n Wiki</a>.)</td>

+</tr></table>

+</div>

+<div class="paragraph"><p>We have to include support for getting available locales manually in an initializer like this:</p></div>

+<div class="listingblock">

+<div class="content"><!-- Generator: GNU source-highlight 2.9

+by Lorenzo Bettini

+http://www.lorenzobettini.it

+http://www.gnu.org/software/src-highlite -->

+<pre><tt><span style="font-style: italic"><span style="color: #9A1900"># config/initializers/available_locales.rb</span></span>

+<span style="font-style: italic"><span style="color: #9A1900">#</span></span>

+<span style="font-style: italic"><span style="color: #9A1900"># Get loaded locales conveniently</span></span>

+<span style="font-style: italic"><span style="color: #9A1900"># See http://rails-i18n.org/wiki/pages/i18n-available_locales</span></span>

+<span style="font-weight: bold"><span style="color: #0000FF">module</span></span> I18n

+  <span style="font-weight: bold"><span style="color: #0000FF">class</span></span> <span style="color: #990000">&lt;&lt;</span> <span style="font-weight: bold"><span style="color: #0000FF">self</span></span>

+    <span style="font-weight: bold"><span style="color: #0000FF">def</span></span> available_locales<span style="color: #990000">;</span> backend<span style="color: #990000">.</span>available_locales<span style="color: #990000">;</span> <span style="font-weight: bold"><span style="color: #0000FF">end</span></span>

+  <span style="font-weight: bold"><span style="color: #0000FF">end</span></span>

+  <span style="font-weight: bold"><span style="color: #0000FF">module</span></span> Backend

+    <span style="font-weight: bold"><span style="color: #0000FF">class</span></span> Simple

+      <span style="font-weight: bold"><span style="color: #0000FF">def</span></span> available_locales<span style="color: #990000">;</span> translations<span style="color: #990000">.</span>keys<span style="color: #990000">.</span>collect <span style="color: #FF0000">{</span> <span style="color: #990000">|</span>l<span style="color: #990000">|</span> l<span style="color: #990000">.</span>to_s <span style="color: #FF0000">}</span><span style="color: #990000">.</span>sort<span style="color: #990000">;</span> <span style="font-weight: bold"><span style="color: #0000FF">end</span></span>

+    <span style="font-weight: bold"><span style="color: #0000FF">end</span></span>

+  <span style="font-weight: bold"><span style="color: #0000FF">end</span></span>

+<span style="font-weight: bold"><span style="color: #0000FF">end</span></span>

+

+<span style="font-style: italic"><span style="color: #9A1900"># You need to "force-initialize" loaded locales</span></span>

+I18n<span style="color: #990000">.</span>backend<span style="color: #990000">.</span>send<span style="color: #990000">(:</span>init_translations<span style="color: #990000">)</span>

+

+AVAILABLE_LOCALES <span style="color: #990000">=</span> I18n<span style="color: #990000">.</span>backend<span style="color: #990000">.</span>available_locales

+RAILS_DEFAULT_LOGGER<span style="color: #990000">.</span>debug <span style="color: #FF0000">"* Loaded locales: #{AVAILABLE_LOCALES.inspect}"</span></tt></pre></div></div>

+<div class="paragraph"><p>You can then wrap the constant for easy access in ApplicationController:</p></div>

+<div class="listingblock">

+<div class="content"><!-- Generator: GNU source-highlight 2.9

+by Lorenzo Bettini

+http://www.lorenzobettini.it

+http://www.gnu.org/software/src-highlite -->

+<pre><tt><span style="font-weight: bold"><span style="color: #0000FF">class</span></span> ApplicationController <span style="color: #990000">&lt;</span> ActionController<span style="color: #990000">::</span>Base

+  <span style="font-weight: bold"><span style="color: #0000FF">def</span></span> available_locales<span style="color: #990000">;</span> AVAILABLE_LOCALES<span style="color: #990000">;</span> <span style="font-weight: bold"><span style="color: #0000FF">end</span></span>

+<span style="font-weight: bold"><span style="color: #0000FF">end</span></span></tt></pre></div></div>

+<h3 id="_setting_locale_from_the_domain_name">2.4. Setting locale from the domain name</h3>

+<div class="paragraph"><p>One option you have is to set the locale from the domain name, where your application runs. For example, we want <tt>www.example.com</tt> to load English (or default) locale, and <tt>www.example.es</tt> to load Spanish locale. Thus the <em>top-level domain name</em> is used for locale setting. This has several advantages:</p></div>

+<div class="ulist"><ul>

+<li>

+<p>

+Locale is an <em>obvious</em> part of the URL

+</p>

+</li>

+<li>

+<p>

+People intuitively grasp in which language the content will be displayed

+</p>

+</li>

+<li>

+<p>

+It is very trivial to implement in Rails

+</p>

+</li>

+<li>

+<p>

+Search engines seem to like that content in different languages lives at different, inter-linked domains

+</p>

+</li>

+</ul></div>

+<div class="paragraph"><p>You can implement it like this in your ApplicationController:</p></div>

+<div class="listingblock">

+<div class="content"><!-- Generator: GNU source-highlight 2.9

+by Lorenzo Bettini

+http://www.lorenzobettini.it

+http://www.gnu.org/software/src-highlite -->

+<pre><tt>before_filter <span style="color: #990000">:</span>set_locale

+<span style="font-weight: bold"><span style="color: #0000FF">def</span></span> set_locale

+  I18n<span style="color: #990000">.</span>locale <span style="color: #990000">=</span> extract_locale_from_uri

+<span style="font-weight: bold"><span style="color: #0000FF">end</span></span>

+<span style="font-style: italic"><span style="color: #9A1900"># Get locale from top-level domain or return nil if such locale is not available</span></span>

+<span style="font-style: italic"><span style="color: #9A1900"># You have to put something like:</span></span>

+<span style="font-style: italic"><span style="color: #9A1900">#   127.0.0.1 application.com</span></span>

+<span style="font-style: italic"><span style="color: #9A1900">#   127.0.0.1 application.it</span></span>

+<span style="font-style: italic"><span style="color: #9A1900">#   127.0.0.1 application.pl</span></span>

+<span style="font-style: italic"><span style="color: #9A1900"># in your /etc/hosts file to try this out locally</span></span>

+<span style="font-weight: bold"><span style="color: #0000FF">def</span></span> extract_locale_from_tld

+  parsed_locale <span style="color: #990000">=</span> request<span style="color: #990000">.</span>host<span style="color: #990000">.</span>split<span style="color: #990000">(</span><span style="color: #FF0000">'.'</span><span style="color: #990000">).</span>last

+  <span style="color: #990000">(</span>available_locales<span style="color: #990000">.</span><span style="font-weight: bold"><span style="color: #0000FF">include</span></span><span style="color: #990000">?</span> parsed_locale<span style="color: #990000">)</span> <span style="color: #990000">?</span> parsed_locale  <span style="color: #990000">:</span> <span style="font-weight: bold"><span style="color: #0000FF">nil</span></span>

+<span style="font-weight: bold"><span style="color: #0000FF">end</span></span></tt></pre></div></div>

+<div class="paragraph"><p>We can also set the locale from the <em>subdomain</em> in very similar way:</p></div>

+<div class="listingblock">

+<div class="content"><!-- Generator: GNU source-highlight 2.9

+by Lorenzo Bettini

+http://www.lorenzobettini.it

+http://www.gnu.org/software/src-highlite -->

+<pre><tt><span style="font-style: italic"><span style="color: #9A1900"># Get locale code from request subdomain (like http://it.application.local:3000)</span></span>

+<span style="font-style: italic"><span style="color: #9A1900"># You have to put something like:</span></span>

+<span style="font-style: italic"><span style="color: #9A1900">#   127.0.0.1 gr.application.local</span></span>

+<span style="font-style: italic"><span style="color: #9A1900"># in your /etc/hosts file to try this out locally</span></span>

+<span style="font-weight: bold"><span style="color: #0000FF">def</span></span> extract_locale_from_subdomain

+  parsed_locale <span style="color: #990000">=</span> request<span style="color: #990000">.</span>subdomains<span style="color: #990000">.</span>first

+  <span style="color: #990000">(</span>available_locales<span style="color: #990000">.</span><span style="font-weight: bold"><span style="color: #0000FF">include</span></span><span style="color: #990000">?</span> parsed_locale<span style="color: #990000">)</span> <span style="color: #990000">?</span> parsed_locale  <span style="color: #990000">:</span> <span style="font-weight: bold"><span style="color: #0000FF">nil</span></span>

+<span style="font-weight: bold"><span style="color: #0000FF">end</span></span></tt></pre></div></div>

+<h3 id="_setting_locale_from_the_url_params">2.5. Setting locale from the URL params</h3>

+<div class="ulist"><ul>

+<li>

+<p>

+TODO : Based on <strong><tt>default_url options</tt></strong>, <a href="http://github.com/karmi/test_default_url_options/blob/master/app/controllers/application.rb#L22-26">http://github.com/karmi/test_default_url_options/blob/master/app/controllers/application.rb#L22-26</a>

+</p>

+</li>

+<li>

+<p>

+TODO : Discussion of plugins (translate_routes and routing_filter)

+</p>

+</li>

+</ul></div>

 <div class="admonitionblock">

 <table><tr>

 <td class="icon">

 <img src="./images/icons/tip.png" alt="Tip" />

 </td>

-<td class="content">For other URL designs, see <a href="http://rails-i18n.org/wiki/pages/how-to-encode-the-current-locale-in-the-url">How to encode the current locale in the URL</a>.</td>

+<td class="content">For setting locale from URL see <a href="http://rails-i18n.org/wiki/pages/how-to-encode-the-current-locale-in-the-url">How to encode the current locale in the URL</a> in the Rails i18n Wiki.</td>

 </tr></table>

 </div>

 <div class="paragraph"><p>Now you&#8217;ve initialized I18n support for your application and told it which locale should be used. With that in place you&#8217;re now ready for the really interesting stuff.</p></div>

@@ -340,7 +477,7 @@ pirate<span style="color: #990000">:</span>
   hello_flash<span style="color: #990000">:</span> Ahoy Flash</tt></pre></div></div>

 <div class="paragraph"><p>There you go. Because you haven&#8217;t changed the default_locale I18n will use English. Your application now shows:</p></div>

 <div class="paragraph"><p><span class="image">

-<img src="images/i18n/demo_translated_english.png" alt="rails i18n demo translated to english" title="rails i18n demo translated to english" />

+<img src="images/i18n/demo_translated_en.png" alt="rails i18n demo translated to english" title="rails i18n demo translated to english" />

 </span></p></div>

 <div class="paragraph"><p>And when you change the URL to pass the pirate locale you get:</p></div>

 <div class="paragraph"><p><span class="image">

@@ -815,9 +952,52 @@ http://www.gnu.org/software/src-highlite -->
           one<span style="color: #990000">:</span>   <span style="color: #FF0000">"1 error prohibited this {{model}} from being saved"</span>

           other<span style="color: #990000">:</span> <span style="color: #FF0000">"{{count}} errors prohibited this {{model}} from being saved"</span>

         body<span style="color: #990000">:</span>    <span style="color: #FF0000">"There were problems with the following fields:"</span></tt></pre></div></div>

-<h3 id="_other_translations_and_localizations">5.2. Other translations and localizations</h3>

-<div class="paragraph"><p>Rails uses fixed strings and other localizations, such as format strings and other format information in a couple of helpers.</p></div>

-<div class="paragraph"><p>TODO list helpers and available keys</p></div>

+<h3 id="_overview_of_other_built_in_methods_that_provide_i18n_support">5.2. Overview of other built-in methods that provide I18n support</h3>

+<div class="paragraph"><p>Rails uses fixed strings and other localizations, such as format strings and other format information in a couple of helpers. Here&#8217;s a brief overview.</p></div>

+<h4 id="_actionview_helper_methods">5.2.1. ActionView helper methods</h4>

+<div class="ulist"><ul>

+<li>

+<p>

+distance_of_time_in_words translates and pluralizes its result and interpolates the number of seconds, minutes, hours and so on. See <a href="http://github.com/rails/rails/blob/master/actionpack/lib/action_view/locale/en.yml#L51">datetime.distance_in_words</a> translations.

+</p>

+</li>

+<li>

+<p>

+datetime_select and select_month use translated month names for populating the resulting select tag. See <a href="http://github.com/rails/rails/blob/master/activesupport/lib/active_support/locale/en.yml#L15">date.month_names</a> for translations. datetime_select also looks up the order option from <a href="http://github.com/rails/rails/blob/master/activesupport/lib/active_support/locale/en.yml#L18">date.order</a> (unless you pass the option explicitely). All date select helpers translate the prompt using the translations in the <a href="http://github.com/rails/rails/blob/master/actionpack/lib/action_view/locale/en.yml#L83">datetime.prompts</a> scope if applicable.

+</p>

+</li>

+<li>

+<p>

+The number_to_currency, number_with_precision, number_to_percentage, number_with_delimiter and humber_to_human_size helpers use the number format settings located in the <a href="http://github.com/rails/rails/blob/master/actionpack/lib/action_view/locale/en.yml#L2">number</a> scope.

+</p>

+</li>

+</ul></div>

+<h4 id="_activerecord_methods">5.2.2. ActiveRecord methods</h4>

+<div class="ulist"><ul>

+<li>

+<p>

+human_name and human_attribute_name use translations for model names and attribute names if available in the <a href="http://github.com/rails/rails/blob/master/activerecord/lib/active_record/locale/en.yml#L43">activerecord.models</a> scope. They also support translations for inherited class names (e.g. for use with STI) as explained above in "Error message scopes".

+</p>

+</li>

+<li>

+<p>

+ActiveRecord::Errors#generate_message (which is used by ActiveRecord validations but may also be used manually) uses human_name and human_attribute_name (see above). It also translates the error message and supports translations for inherited class names as explained above in "Error message scopes".

+</p>

+</li>

+<li>

+<p>

+ActiveRecord::Errors#full_messages prepends the attribute name to the error message using a separator that will be looked up from <a href="http://github.com/rails/rails/blob/master/actionpack/lib/action_view/locale/en.yml#L91">activerecord.errors.format.separator</a> (and defaults to ' ').

+</p>

+</li>

+</ul></div>

+<h4 id="_activesupport_methods">5.2.3. ActiveSupport methods</h4>

+<div class="ulist"><ul>

+<li>

+<p>

+Array#to_sentence uses format settings as given in the <a href="http://github.com/rails/rails/blob/master/activesupport/lib/active_support/locale/en.yml#L30">support.array</a> scope.

+</p>

+</li>

+</ul></div>

 </div>

 <h2 id="_customize_your_i18n_setup">6. Customize your I18n setup</h2>

 <div class="sectionbody">

@@ -868,16 +1048,75 @@ http://www.lorenzobettini.it
 http://www.gnu.org/software/src-highlite -->

 <pre><tt>I18n<span style="color: #990000">.</span>t <span style="color: #990000">:</span>foo<span style="color: #990000">,</span> <span style="color: #990000">:</span><span style="font-weight: bold"><span style="color: #0000FF">raise</span></span> <span style="color: #990000">=&gt;</span> <span style="font-weight: bold"><span style="color: #0000FF">true</span></span> <span style="font-style: italic"><span style="color: #9A1900"># always re-raises exceptions from the backend</span></span></tt></pre></div></div>

 </div>

-<h2 id="_resources">7. Resources</h2>

+<h2 id="_conclusion">7. Conclusion</h2>

+<div class="sectionbody">

+<div class="paragraph"><p>At this point you hopefully have a good overview about how I18n support in Ruby on Rails works and are ready to start translating your project.</p></div>

+<div class="paragraph"><p>If you find anything missing or wrong in this guide please file a ticket on <a href="http://i18n.lighthouseapp.com/projects/14948-rails-i18n/overview">our issue tracker</a>. If you want to discuss certain portions or have questions please sign up to our <a href="http://groups.google.com/group/rails-i18n">mailinglist</a>.</p></div>

+</div>

+<h2 id="_contributing_to_rails_i18n">8. Contributing to Rails I18n</h2>

+<div class="sectionbody">

+<div class="paragraph"><p>I18n support in Ruby on Rails was introduced in the release 2.2 and is still evolving. The project follows the good Ruby on Rails development tradition of evolving solutions in plugins and real applications first and then cherry-picking the best bread of most widely useful features second for inclusion to the core.</p></div>

+<div class="paragraph"><p>Thus we encourage everybody to experiment with new ideas and features in plugins or other libraries and make them available to the community. (Don&#8217;t forget to announce your work on our <a href="http://groups.google.com/group/rails-i18n">mailinglist</a>!)</p></div>

+<div class="paragraph"><p>If you find your own locale (language) missing from our <a href="http://github.com/svenfuchs/rails-i18n/tree/master/rails/locale">example translations data</a> repository for Ruby on Rails</p></div>

+</div>

+<h2 id="_resources">9. Resources</h2>

 <div class="sectionbody">

+<div class="ulist"><ul>

+<li>

+<p>

+<a href="http://rails-i18n.org">rails-i18n.org</a> - Homepage of the rails-i18n project. You can find lots of useful resources on the <a href="http://rails-i18n.org/wiki">wiki</a>.

+</p>

+</li>

+<li>

+<p>

+<a href="http://groups.google.com/group/rails-i18n">rails-i18n Google group</a> - The project&#8217;s mailinglist.

+</p>

+</li>

+<li>

+<p>

+<a href="http://github.com/svenfuchs/rails-i18n/tree/master">Github: rails-i18n</a> - Code repository for the rails-i18n project. Most importantly you can find lots of <a href="http://github.com/svenfuchs/rails-i18n/tree/master/rails/locale">example translations</a> for Rails that should work for your application in most cases.

+</p>

+</li>

+<li>

+<p>

+<a href="http://i18n.lighthouseapp.com/projects/14948-rails-i18n/overview">Lighthouse: rails-i18n</a> - Issue tracker for the rails-i18n project.

+</p>

+</li>

+<li>

+<p>

+<a href="http://github.com/svenfuchs/i18n/tree/master">Github: i18n</a> - Code repository for the i18n gem.

+</p>

+</li>

+<li>

+<p>

+<a href="http://i18n.lighthouseapp.com/projects/14947-ruby-i18n/overview">Lighthouse: i18n</a> - Issue tracker for the i18n gem.

+</p>

+</li>

+</ul></div>

+</div>

+<h2 id="_authors">10. Authors</h2>

+<div class="sectionbody">

+<div class="ulist"><ul>

+<li>

+<p>

+Sven Fuchs[http://www.workingwithrails.com/person/9963-sven-fuchs] (initial author)

+</p>

+</li>

+<li>

+<p>

+Karel Minarik[http://www.workingwithrails.com/person/7476-karel-mina-k]

+</p>

+</li>

+</ul></div>

+<div class="paragraph"><p>If you found this guide useful please consider recommending its authors on <a href="http://www.workingwithrails.com">workingwithrails</a>.</p></div>

 </div>

-<h2 id="_footnotes">8. Footnotes</h2>

+<h2 id="_footnotes">11. Footnotes</h2>

 <div class="sectionbody">

 <div class="paragraph"><p><a id="1"></a>[1] Or, to quote <a href="http://en.wikipedia.org/wiki/Internationalization_and_localization">Wikipedia</a>: <em>"Internationalization is the process of designing a software application so that it can be adapted to various languages and regions without engineering changes. Localization is the process of adapting software for a specific region or language by adding locale-specific components and translating text."</em></p></div>

 <div class="paragraph"><p><a id="2"></a>[2] Other backends might allow or require to use other formats, e.g. a GetText backend might allow to read GetText files.</p></div>

 <div class="paragraph"><p><a id="3"></a>[3] One of these reasons is that we don&#8217;t want to any unnecessary load for applications that do not need any I18n capabilities, so we need to keep the I18n library as simple as possible for English. Another reason is that it is virtually impossible to implement a one-fits-all solution for all problems related to I18n for all existing languages. So a solution that allows us to exchange the entire implementation easily is appropriate anyway. This also makes it much easier to experiment with custom features and extensions.</p></div>

 </div>

-<h2 id="_changelog">9. Changelog</h2>

+<h2 id="_changelog">12. Changelog</h2>

 <div class="sectionbody">

 <div class="paragraph"><p><a href="http://rails.lighthouseapp.com/projects/16213/tickets/23">Lighthouse ticket</a></p></div>

 </div>