# Issues in 0.3.3

**URL:** <https://www.ruby-forum.com/t/issues-in-0-3-3/181510>\
**Category:** Rails I18n\
**Created:** [January 12, 2010, 11:40pm UTC](https://www.ruby-forum.com/t/issues-in-0-3-3/181510 "2010-01-12T23:40:49Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![knapo](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/k/ba9def/32.png) [@knapo](https://www.ruby-forum.com/u/knapo)\
**Post date:** [January 12, 2010, 11:40pm UTC](https://www.ruby-forum.com/t/issues-in-0-3-3/181510/1 "2010-01-12T23:40:49Z")

</div>

Hi,

After great Jose’s article at

> **[Run, I18n, run! « Plataformatec Blog](http://blog.plataformatec.com.br/2009/12/run-i18n-run/)**
>
> A new I18n gem just got released and it comes with two new backends extensions: Fast and InterpolationCompiler. First, what is a backend? I18n.t, I18n.translate, I18n.l and I18n.localize methods are actually just wrappers to I18n.backend, which is...

I started using 0.3.3 (thanks for great improvements!), unfortunately  
had some issue I reported on [Issues · ruby-i18n/i18n · GitHub](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-latest-i18n-gem](http://blog.knapo.net/2010/1/12/my-improvements-on-latest-i18n-gem)

Regards,  
Krzysztof K.

---

<div class="post-metadata">

**Author:** ![knapo](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/k/ba9def/32.png) [@knapo](https://www.ruby-forum.com/u/knapo)\
**Post date:** [January 17, 2010, 11:47am UTC](https://www.ruby-forum.com/t/issues-in-0-3-3/181510/2 "2010-01-17T11:47:54Z")

</div>

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  
[Issues · ruby-i18n/i18n · GitHub](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!

---

<div class="post-metadata">

**Author:** ![knapo](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/k/ba9def/32.png) [@knapo](https://www.ruby-forum.com/u/knapo)\
**Post date:** [January 17, 2010, 2:33pm UTC](https://www.ruby-forum.com/t/issues-in-0-3-3/181510/3 "2010-01-17T14:33:31Z")

</div>

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: [Issues · ruby-i18n/i18n · GitHub](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/load\_path.rb](http://github.com/knapo/i18n/blob/master/lib/i18n/load_path.rb)

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

> <https://github.com/joshmh/globalize2/blob/8eba0228b70225958dca2fcf0255b55237d67036/lib/globalize/load_path.rb>

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!

---

<div class="post-metadata">

**Author:** ![knapo](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/k/ba9def/32.png) [@knapo](https://www.ruby-forum.com/u/knapo)\
**Post date:** [January 17, 2010, 11:40pm UTC](https://www.ruby-forum.com/t/issues-in-0-3-3/181510/4 "2010-01-17T23:40:09Z")

</div>

Hi Sven,

2010/1/17 Sven F. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid):

> I’ve fixed 4 of the issues, closed the tickets and commented on the sixth one: [Issues · ruby-i18n/i18n · GitHub](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/load\_path.rb](http://github.com/knapo/i18n/blob/master/lib/i18n/load_path.rb)
> 
> 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
