Globalize2 Globalize2

Comments and changes to this ticket

• 

  Josh H February 17th, 2009 @ 08:13 PM

  • → State changed from “new” to “open”

  Looks good to me. Any objections?

• 

  Sven Fuchs February 17th, 2009 @ 08:57 PM

  looks cool :)

• 

  Sébastien Grosjean - ZenCocoon February 22nd, 2009 @ 09:32 AM

  do you like a push request Josh ?

• 

  tim February 16th, 2010 @ 06:07 PM

  we added a little hack to define seperate methods for each localized attribute.

  for example: i have a post object, the content attribute is translated into german and english..

  class Post
   translates :content
  end
  

  generates
  

  Post.new.content_de and Post.new.content_en.
  

  We use this to added a form with this 2 attributes to add translations to the post content. This just works seemless with the way how rails works with forms and attributes...

  our code
  

  module Ours
    module Globalize
  
  
  
  
  
  
  

  def translates(*attr)
    attr.each do |name|
      I18n.available_locales.each do |locale|
        define_method "#{name}_#{locale}" do
          #globalize.fetch locale, name
          translations.select{|t| t.locale == locale}.first.try(name)
        end
        define_method "#{name}_#{locale}=" do |value|
          value = value.blank? ? nil : value
          globalize.write(locale, name, value)
          #self[name] = value
        end
      end
    end
    super
  end
  

  
  
  
  
    end
  end
  
  
  
  class Post
    extend Ours::Globalize
    translates :content
  end
  

• 

  Sébastien Grosjean - ZenCocoon February 16th, 2010 @ 06:43 PM

  • no changes were found...
• 

  Sébastien Grosjean - ZenCocoon February 16th, 2010 @ 06:50 PM

  not a big fan of this hack personally.

  I've started a different path a while ago, you can find more at http://globalize2.lighthouseapp.com/projects/15085/tickets/6-add-lo... or even http://globalize2.lighthouseapp.com/projects/15085/tickets/10-featu...