Skip to content
Browse files

en-AU translations for original en-US file; seems that some are missing

  • Loading branch information...
1 parent 910ddda commit 5dab111dda3e2b2215b634827b40aa5826964478 @drnic drnic committed Aug 28, 2008
Showing with 18 additions and 16 deletions.
  1. +1 −0 .gitignore
  2. +3 −2 app/views/layouts/application.html.erb
  3. +14 −14 config/locales/en-AU.rb
  4. 0 log/development.log
View
1 .gitignore
@@ -2,3 +2,4 @@
log/*.log
tmp/**/*
db/schema.rb
+db/*.sqlite3
View
5 app/views/layouts/application.html.erb
@@ -32,8 +32,9 @@
<div id="footer">
<p><%= I18n.t 'txt.main_title' %> - <%= I18n.t 'txt.app_name' %></p>
<p>&copy; 2008 Clemens Kofler &lt;<%= mail_to 'clemens@railway.at' %>&gt;</p>
- <p>Traduzido para português brasileiro por <%= link_to 'Fabio Akita', 'http://www.akitaonrails.com/' %></p>
- <p>Content Translation work & Japanese - <%= link_to "Simon Tokumine", "mailto:simon@japancentre.com" %> & <%= link_to "Masayuki Nakamura", "mailto:masayuki@japancentre.com" %></p>
+ <p>Traduzido para português brasileiro por <%= link_to 'Fabio Akita', 'http://www.akitaonrails.com/' %></p>
+ <p>Content Translation work & Japanese - <%= link_to "Simon Tokumine", "mailto:simon@japancentre.com" %> & <%= link_to "Masayuki Nakamura", "mailto:masayuki@japancentre.com" %></p>
+ <p>True Blue Australian lingo - <%= link_to "Dr Nic Williams", "http://drnicwilliams.com" %></p>
<p><%= link_to 'www.railway.at - welcome aboard!', 'http://www.railway.at' %></p>
<p style="position:absolute; bottom:25px; right:25px;"><%= link_to image_tag("http://i.creativecommons.org/l/by-nc-sa/2.0/at/88x31.png"), "http://creativecommons.org/licenses/by-nc-sa/2.0/at/" %></p>
</div>
View
28 config/locales/en-AU.rb
@@ -1,10 +1,10 @@
-I18n.backend.store_translations :'en-US', {
+I18n.backend.store_translations :'en-AU', {
:date => {
:formats => {
- :default => "%Y-%m-%d",
+ :default => "%d/%m/%Y",
:short => "%e %b",
- :long => "%B %e, %Y",
- :long_ordinal => lambda { |date| "%B #{date.day.ordinalize}, %Y" }
+ :long => "%e %B, %Y",
+ :long_ordinal => lambda { |date| "#{date.day.ordinalize} %B, %Y" }
},
:day_names => Date::DAYNAMES,
:abbr_day_names => Date::ABBR_DAYNAMES,
@@ -17,8 +17,8 @@
:default => "%a %b %d %H:%M:%S %Z %Y",
:time => "%H:%M",
:short => "%d %b %H:%M",
- :long => "%B %d, %Y %H:%M",
- :long_ordinal => lambda { |time| "%B #{time.day.ordinalize}, %Y %H:%M" }
+ :long => "%d %B, %Y %H:%M",
+ :long_ordinal => lambda { |time| "#{time.day.ordinalize} %B, %Y %H:%M" }
},
:datetime => {
:formats => {
@@ -34,9 +34,9 @@
:pm => 'pm'
} ,
:txt => {
- :main_title => "Localizing Rails",
+ :main_title => "Localising Rails",
:app_name => "Demo Application",
- :sub_title => "how to localize your app with Rails' new i18n features",
+ :sub_title => "CRIKEY! - how to localise your awesome apps with Rails' new i18n features",
:contents => "Contents",
:menu => {
:introduction => "Introduction",
@@ -52,8 +52,8 @@
:licence => "This demo app and all its contents are licensed under the {{licence_href}}. If you want to use it in ways prohibited by this license, please contact me and ask my permission."
},
:active_record => {
- :too_lazy => "No examples here since I'm too lazy to think of attributes to show <strong>all</strong> custom error messages. ;-)",
- :easy_to_understand => "It's quite easy to understand, though."
+ :too_lazy => "Bugger. No examples here since I'm too lazy to think of attributes to show <strong>all</strong> custom error messages. ;-)",
+ :easy_to_understand => "It's quite easy to understand, though, champ."
},
:date_formats => {
:rails_standards_work => "Rails standard formats (Date::DATE_FORMATS) still work:"
@@ -63,7 +63,7 @@
:forms_title => "Forms"
},
:index => {
- :introduction => "Lately, a lot of work has been done by {{sven_blog}} and {{sven_github}} to facilitate future internationalization and localization of Rails.",
+ :introduction => "Strewth! Lately, a lot of work has been done by {{sven_blog}} and {{sven_github}} to facilitate future internationalization and localization of Rails.",
:story_so_far => "This demo app tries to show you how you can use the features that have been implemented so far to localize big parts of your Rails application."
},
:number_helper => {
@@ -75,9 +75,9 @@
:you_need_to_be_on_edge => "You need to be on Edge Rails in order to use the Rails i18n features:",
:date_time_formats => "For date and time formats, you also need to install the {{localized_dates_link}}:",
:config_locale => "Configuring the locale",
- :best_place => "The best place to put your locale configuration, in my opinion, is <code>config/locales</code>. The localized_dates plugin will copy two locales, en-US and de-AT, in this directory. You can extend or modify them and also create new locales.",
+ :best_place => "The best place to put your locale configuration, in my opinion, is <code>config/locales</code>. The localized_dates plugin will copy two locales, en-US and de-AT, in this directory. You can extend or modify them and also create new locales, such as this en-AU locale. Ozzie Ozzie Ozzie!",
:locale => "Here's the demo locale that was used for this demo application:",
- :defaults => "You also need to set up the default locale and/or locale in your <code>environment.rb</code> or an initializer.",
+ :defaults => "You also need to set up the default locale and/or locale in your <code>environment.rb</code> or an initialiser.",
:locale_structure_title => "A word on the structure of locales",
:locale_structure_number => "You may have noticed that inside the <code>:number</code> part of the locale, we defined <code>:format</code> and <code>:currency</code>. In general, locales are structured hierarchically - i.e. a currencies are numbers, percentages are numbers, etc. <code>:currency</code> can either override the basic <code>:format</code> settings (in our case, we set <code>:precision</code> to 2 instead of 3) or extend them (we add two new options, <code>:unit</code> and <code>:format</code>).",
:locale_structure_date_time => "The same holds true for dates and times: If needed, <code>:datetime</code> and <code>:time_with_zone</code> can be used to specifically address formatting of their respective types instead of just relying on the settings for <code>:time</code>. Note, however, that usually you want to use the same formats as <code>:time</code>."
@@ -86,7 +86,7 @@
:rails_standards_work => "Rails standard formats (Time::DATE_FORMATS) still work:"
},
:ipe => {
- :click => "click here!"
+ :click => "click here, mate!"
}
}
}
View
0 log/development.log
No changes.

0 comments on commit 5dab111

Please sign in to comment.
Something went wrong with that request. Please try again.