Comments on: Internationalisation in edge Rails http://cameronyule.com/2008/07/internationalisation-in-edge-rails Glasgow based new media developer Cameron Yule. Fri, 21 Nov 2008 14:05:20 +0000 http://wordpress.org/?v=2.6.3 By: Cameron http://cameronyule.com/2008/07/internationalisation-in-edge-rails#comment-99 Cameron Wed, 23 Jul 2008 19:03:05 +0000 http://cameronyule.com/?p=82#comment-99 Hi Thomas. Yeah, you might be right about the way Globalite stores it's translation files in YAML not changing - I guess from an existing-user point of view that'd make sense. The reason I mentioned using ruby files (aside from the benefits I mentioned in the post) was that the new 'simple' back-end that Rails uses to localise to en-US is using ruby files also. Probably some as-yet unreleased plugin which functions similar to Globalite will appear and I'll move to that. As you say - good news indeed. :) Hi Thomas. Yeah, you might be right about the way Globalite stores it’s translation files in YAML not changing - I guess from an existing-user point of view that’d make sense.

The reason I mentioned using ruby files (aside from the benefits I mentioned in the post) was that the new ’simple’ back-end that Rails uses to localise to en-US is using ruby files also.

Probably some as-yet unreleased plugin which functions similar to Globalite will appear and I’ll move to that.

As you say - good news indeed. :)

]]> By: Thomas Nichols http://cameronyule.com/2008/07/internationalisation-in-edge-rails#comment-98 Thomas Nichols Wed, 23 Jul 2008 18:06:21 +0000 http://cameronyule.com/?p=82#comment-98 We're using Globalite too, and loving it (apart from occasional weird __localization_missing__ errors). IIUC, though, the rails i18n support isn't going to change the way the backend works; I'm guessing our existing :hello.l calls will need to change to :hello.t and similar API changes, but that the backend will stay the same. It seems "Hello {name}" becomes "Hello {{name}}", but otherwise it looks as though our existing translated yamls won't need much tweaking. And if you don't like yaml, you'll be able to switch to GeText po/mo files or use Globalize and shove it all in the db. Looks like good news to me. -- Thomas. We’re using Globalite too, and loving it (apart from occasional weird __localization_missing__ errors). IIUC, though, the rails i18n support isn’t going to change the way the backend works; I’m guessing our existing :hello.l calls will need to change to :hello.t and similar API changes, but that the backend will stay the same.

It seems “Hello {name}” becomes “Hello {{name}}”, but otherwise it looks as though our existing translated yamls won’t need much tweaking. And if you don’t like yaml, you’ll be able to switch to GeText po/mo files or use Globalize and shove it all in the db. Looks like good news to me.

– Thomas.

]]>