2010/1/17 Sven F. [email protected]:
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:
name: “name in pl”
I will get “name” for User.human_attribute_name(:name), what’s not
One thing though. Do you really think that claiming authorship for this one is correct?
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