I18n, look up a translation with the default locale when it's missed with another specific locale

We were just looking for this kind of solution few days ago. For us is better to display english translation than displaying a missing key text.

great

Globalize2 also has a very good solution for this problem: http://wiki.github.com/joshmh/gl...

Globalize2 also has a very good solution to this problem: http://wiki.github.com/joshmh/gl...

+1, nice patch! My users will also prefer an english text better than a "missing key" warning.

Ugh I meant +1 in my last comment. I wonder how that got interpreted as a new ordered list item!

• 1, Nice patch.

We already had this discussion on the I18n group when we decided to not add this functionality. But since it was implemented as an option, +1 for me.

The patch works here, but anyway I think it should be sent to the Rails I18n tracker:

http://i18n.lighthouseapp.com/projects/14948-rails-i18n/tickets?q=all

It would be nice to check if it works on Rails setup as well (it probably works by default):

config.i18n.use_default_locale_on_missing_translation = true

Yep, I didn't know there were a separate project. I'm sending it to the I18n tracker as well.

It already works on Rails setup by default, this is the code that initialize the I18n options:

@@@ruby configuration.i18n.each do |setting, value|

    if setting == :load_path
      I18n.load_path += value
    else
      I18n.send("#{setting}=", value)
    end

end

Nice Job Calavera!

Incidentally, this is one of the main reasons I still use Gettext, it allows me to concentrate on the main language and add translations progressively.

Cheers, sam

Would love to see it implemented, as an option is the way to go.

+1 nice! I like this patch, very usefull.

Sorry Sven but I don't agree on deciding that this wont be fixed.

Having a fallback language it's something Gettext has been doing for ages and I18n should do the same by default, in fact there's a lot of people who expects this behavior.

Meanwhile I've extended the object class to achieve the behavior I wanted to have.

class Object

  def _(msg, *args)
    options = args.extract_options!
    options[:default] = msg
    I18n.t(msg, options)
  end

end

Francesc, I'm sure a lot of people use fallbacks. That doesn't mean it must be included to Rails though right now though. Rails I18n was built to support no other locale than :en out of the box. The reason for this is that it can be incredibly hard to figure out "the right way" to do it - and Gettext is not always a good example.

Please keep in mind that experimenting with advanced features in plugin-land, then comparing solutions, maybe cherrypicking a few things from the best breeds and then including them into the I18n lib in a defensive way is part of the plan :)

Does Globalize2 fallback support solve your problem? If so we should better document (e.g. in the I18n guide) that it's there and how it can be used. If not, please provide feedback so it can be improved.

In my opinion falling back to the message user has provided if no translation available it's a good solution, this makes me think that although my application is in english I always have to translate it creating locale files. In my opinion:

t("Hello World") should become "Hello World" if no translation available.

Users don't have to see those "missing translation" & "en, Hello World" warnings.

Gettext maybe it's not a good example, but makes sense to return the same message if no translation is available. (Other thing is how it's implemented)

(I must say I understand it's hard to figure the right way to do it.)

louis vuitton watches