Forum: Rails I18n issues in 0.3.3

Hi,

After great Jose's article at 
http://blog.plataformatec.com.br/2009/12/run-i18n-run/
I started using 0.3.3 (thanks for great improvements!), unfortunately
had some issue I reported on http://github.com/svenfuchs/i18n/issues.

Here are described fixes and more thoughts about new i18n:
http://blog.knapo.net/2010/1/12/my-improvements-on...

Regards,
Krzysztof Knapik

Hi Krzysztof!

First of all, sorry for not being able to reply earlier. This was a 
crazy week.

I've reviewed the issues that you've added to 
http://github.com/svenfuchs/i18n/issues and I agree these are simply 
bugs.

I've also had a look at your fork and patches. Unfortunately you haven't 
added any tests, so it's hard to simply cherry-pick things. I'll go 
ahead and add tests at least for the bugs you've reported (not sure 
about the additional features like load_path, yet).

Thanks for your work!

Hi Krzysztof,

thanks a lot for filing these tickets!

I've fixed 4 of the issues, closed the tickets and commented on the 
sixth one: http://github.com/svenfuchs/i18n/issues#issue/5

I currently don't think this is a bug but actually the correct 
behaviour. Could you please provide example scenarios where you want 
fallback locale lookups take precedence over defaults? (See the example 
given in the ticket comment above.)


One thing though. Do you really think that claiming authorship for this 
one is correct?

http://github.com/knapo/i18n/blob/master/lib/i18n/...

It's quite obviously a slightly modified version of the Globalize2 
LoadPath.

http://github.com/joshmh/globalize2/blob/8eba0228b...

We've decided against moving this functionality to I18n a while ago. You 
might want to make it a plugin instead. But if you open source it 
somewhere, please be sure to maintain the actual authorship.

Thanks!

Hi Sven,

2010/1/17 Sven Fuchs <svenfuchs@artweb-design.de>:
> I've fixed 4 of the issues, closed the tickets and commented on the sixth one: http://github.com/svenfuchs/i18n/issues#issue/5

Thanks a lot. You found much better and consistent way to fix them
(all together :) )

> I currently don't think this is a bug but actually the correct behaviour. Could you please provide example scenarios where you want fallback locale lookups take precedence over defaults? (See the example given in the ticket comment above.)

As I wrote in ticket comment, the example is
ActiveRecord::Base#human_attribute_name method which always passes
default which is a attribute_key_name.to_s.humanize string.

So e.g. when I set locale to pl-PL and have:
pl:
  activerecord:
    attributes:
      user:
        name: "name in pl"
I will get "name" for User.human_attribute_name(:name), what's not 
correct.


> One thing though. Do you really think that claiming authorship for this one is correct?
>
> http://github.com/knapo/i18n/blob/master/lib/i18n/...
>
> It's quite obviously a slightly modified version of the Globalize2 LoadPath.

I absolutely don't think (shame on me). Thanks for taking a notice.

> We've decided against moving this functionality to I18n a while ago.

I agree. In most cases it's not such a valuable thing to put its into 
core I18n.

Thanks!

KK