Comments on: Internationalization features in Rails edge http://blog.phusion.nl/2008/08/27/internationalization-features-in-rails-edge/ Mon, 06 Sep 2010 12:55:09 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: hongli http://blog.phusion.nl/2008/08/27/internationalization-features-in-rails-edge/comment-page-1/#comment-1009 hongli Sat, 06 Sep 2008 16:08:26 +0000 http://blog.phusion.nl/?p=44#comment-1009 Thanks for the heads-up. The demo app is a bit unstable so I had to restart it. Thanks for the heads-up. The demo app is a bit unstable so I had to restart it.

]]> By: Tejo http://blog.phusion.nl/2008/08/27/internationalization-features-in-rails-edge/comment-page-1/#comment-1008 Tejo Sat, 06 Sep 2008 15:48:41 +0000 http://blog.phusion.nl/?p=44#comment-1008 actually the demo page says: 502 Bad Gateway actually the demo page says: 502 Bad Gateway

]]> By: Adam http://blog.phusion.nl/2008/08/27/internationalization-features-in-rails-edge/comment-page-1/#comment-860 Adam Tue, 02 Sep 2008 23:29:53 +0000 http://blog.phusion.nl/?p=44#comment-860 no-BM is broken no-BM is broken

]]> By: kent http://blog.phusion.nl/2008/08/27/internationalization-features-in-rails-edge/comment-page-1/#comment-678 kent Wed, 27 Aug 2008 23:32:19 +0000 http://blog.phusion.nl/?p=44#comment-678 site layout is broken under Safari though. site layout is broken under Safari though.

]]> By: Simon Tokumine http://blog.phusion.nl/2008/08/27/internationalization-features-in-rails-edge/comment-page-1/#comment-677 Simon Tokumine Wed, 27 Aug 2008 22:34:03 +0000 http://blog.phusion.nl/?p=44#comment-677 Thanks for the write-up Hongli. I can't take much of the credit however. The timeline of the demo is: Clemens Kofler wrote the vast bulk of the project as an i18n explanation in English. Fabio Akita wrote a port of the project in Brazilian Portuguese Me and Masayuki Nakamura brought both languages together, added locale switching, did a Japanese translation and i18n'd the interface. One of the perils of git I suppose! It's not perfect (no YML support yet), but can be extended by dropping in a translation file into the config/locale directory. A big thanks go to the i18n team for making this sort of thing possible in Plain Old Rails. We do live in a world full of different languages and i18n deserves to be in the core. This and the UTF-8 changes in 1.2 are greatly enhancing the attraction of Rails in non English speaking countries, which can only be a good thing. It makes you wonder what Jeremy Kemper will wish for next... To follow the latest developments in the run up to 2.2, follow the google groups: http://groups.google.com/group/rails-i18n Thanks for the write-up Hongli. I can’t take much of the credit however. The timeline of the demo is:

Clemens Kofler wrote the vast bulk of the project as an i18n explanation in English.
Fabio Akita wrote a port of the project in Brazilian Portuguese
Me and Masayuki Nakamura brought both languages together, added locale switching, did a Japanese translation and i18n’d the interface.

One of the perils of git I suppose!

It’s not perfect (no YML support yet), but can be extended by dropping in a translation file into the config/locale directory.

A big thanks go to the i18n team for making this sort of thing possible in Plain Old Rails. We do live in a world full of different languages and i18n deserves to be in the core. This and the UTF-8 changes in 1.2 are greatly enhancing the attraction of Rails in non English speaking countries, which can only be a good thing. It makes you wonder what Jeremy Kemper will wish for next…

To follow the latest developments in the run up to 2.2, follow the google groups: http://groups.google.com/group/rails-i18n

]]>