github/rails
1
1
Fork 0
mirror of https://github.com/github/rails.git synced 2026-04-26 03:00:59 -04:00
Code Issues Packages Projects Releases Wiki Activity

Add links to lighthouse ticket for i18n guide

Browse Source
This commit is contained in:
Pratik Naik
2009-01-18 00:31:42 +00:00
parent 56152d8f60
commit 69022dfd7b
4 changed files with 7 additions and 16 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
railties/doc/guides/html/i18n.html
View File

@@ -103,10 +103,7 @@
<a href="#_footnotes">Footnotes</a>
</li>
<li>
<a href="#_credits">Credits</a>
</li>
<li>
<a href="#_notes">NOTES</a>
<a href="#_changelog">Changelog</a>
</li>
</ol>
</div>
@@ -850,12 +847,9 @@ http://www.gnu.org/software/src-highlite -->
<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="_credits">9. Credits</h2>
<h2 id="_changelog">9. Changelog</h2>
<div class="sectionbody">
</div>
<h2 id="_notes">10. NOTES</h2>
<div class="sectionbody">
<div class="paragraph"><p>How to contribute?</p></div>
<div class="paragraph"><p><a href="http://rails.lighthouseapp.com/projects/16213/tickets/23">Lighthouse ticket</a></p></div>
</div>
</div>

2
railties/doc/guides/html/index.html
View File

@@ -196,7 +196,7 @@ of your code.</p></div>
<td class="icon">
<img src="./images/icons/caution.png" alt="Caution" />
</td>
<td class="content">still a basic draft</td>
<td class="content"><a href="http://rails.lighthouseapp.com/projects/16213/tickets/23">Lighthouse ticket</a></td>
</tr></table>
</div>
<div class="paragraph"><p>This guide introduces you to the basic concepts and features of the Rails I18n API and shows you how to localize your application.</p></div>

7
railties/doc/guides/source/i18n.txt
View File

@@ -644,9 +644,6 @@ I18n.t :foo, :raise => true # always re-raises exceptions from the backend
[[[3]]] One of these reasons is that we don'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.
== Credits
== NOTES
How to contribute?
== Changelog ==
http://rails.lighthouseapp.com/projects/16213/tickets/23[Lighthouse ticket]

2
railties/doc/guides/source/index.txt
View File

@@ -125,7 +125,7 @@ This guide covers how to build a plugin to extend the functionality of Rails.
.link:i18n.html[The Rails Internationalization API]
***********************************************************
CAUTION: still a basic draft
CAUTION: link:http://rails.lighthouseapp.com/projects/16213/tickets/23[Lighthouse ticket]
This guide introduces you to the basic concepts and features of the Rails I18n API and shows you how to localize your application.
***********************************************************