Rails Internationalization
?Download as ZIP, PDF?
1 like?1,893 views
An overview of the Rails i18n functionality and lessons learned from working to internationalize our application. Official Rails i18n support is still relatively new & continuing to mature. Will also cover our Translator plugin we're developing to simplify the process of externalizing strings & testing an internationalized app.
Editor's Notes
- #2: - Turn off Growl / IM / Twitterffic / Gmail notifications
- #5: - Quick overview of Rails and i18n. - Long topic -- people write books on this!
- #6: - “m2e c6n” - Better at computer languages than human ones - Not an I18n expert / knowledge welcome - SML has users from every country - Talk comes from our work to i18n our Rails app
- #7: - Ask: how many have had pleasure of internationalizing an application? - 0: Rails 1.2 added UTF-8 support for string manipulation. Ruby 1.9 adds real UTF-8 support - 1: DHH (Dane) + Matz (Japanese) == English-only? - 1: Rails core is now i18n’d, and only localized to English
- #8: - Can affect data model! Address shouldn’t expect 5-digit ZIP code - People might not use “first name” “last name” - A mailbox icon might not register as “email”. Images of red traffic light for “stop”.
- #9: - Lots of issues to think about - Sorry for the bad Spanish
- #14: - The more languages you see, the more Erlang & Haskell look normal - If you like gory details about diacritic marks, tertiary sorting criteria and standards you’ll love this!
- #16: - Extraction from what we’ve learned at SML - End up having some strings in controllers (flash), mailers (subject lines), models (errors) - Mention scoping backoff for key hierarchy
- #18: - British English vs. American English - In Japan, but prefer English