MailingList


Re: a proposed solution for localized templates

by Nicola Piccinini :: Rate this Message:

Reply to Author | View in Thread

it's a clever idea, I believe.

I can say that I was using globalize with RoR 2.0.2 for a while with
that ActionView code commented out. Everything seems to work correctly
with the obvious exception of template localization.

Btw, in this days I had the hare-brained idea to switch to the "soon
to be released" RoR 2.1.
The good news is that most of Globalize continue to work but not all
and so I had to write some patches.

We all know that Rails has moved to git, this SCM tool should be very
efficient in managing distributed development and probably also
Globalize could benefit of this sort of organization.
So I created a personal space at github and I forked Globalize
starting from trunk@183:
http://github.com/pic/globalize

Then I committed my patches so anyone can look at them, any comment is
well appreciated.

In current status the test suite is broken for every test regarding
template localization, in fact I removed action_view.rb without
implementing an alternative solution.
Moreover I had to disable a lot of tests of date helpers because with
RoR 2.1 the order of attributes in rendering an <option> tag is
changed. I don't know how much solid is testing those helpers with
string comparisons, how can we be sure that RoR will render:

<option selected="selected" value="10">

instead of

<option value="10" selected="selected">

in any possible environment?

Anyway for my needs the current status is more than sufficient.

Let me know If my fork of Globalize on a github repository is
inappropriate that I'll remove it in a minute.

Nicola

 « Return to Thread: a proposed solution for localized templates