Thanks,
Dmitry

before_save :cleanup_fields
 
private
 
def cleanup_fields
  available_columns_of("description").each do |column|
    send("#{column}=", nil) if send(column).blank?
  end
end

You can also use the attribute normalization plugin

I really like that plugin, just works the way I need it in most cases, for websites using 2-3 languages, in my case french, english and german.

One thing I really like to offer to my clients is simple forms where some datas wil be translated, some won’t for example last name, first name, or company name would not be translated, while a presentation text could be written in 3 languages.

this is when I love to have for example 3 text areas, using transalted columns:

description_fr
description_en
description_de

letting my user decide in what language they wish to fill their description.

it works almost as I would expect, the use_default is fantastic, but I just have a problem: as the forms are submitted with all the transalted fields, if they are left blank the form, they are saved as blank string, instead of nil.

in that case, when the page containing the datas is loaded, instead of getting a default value it just gives me an empty string.

I made an ugly fix, in my model, using a “before save” in my model, but it’s so ugly….

def before_save
if self. description_fr.blank?
self. description_fr=nil
end
if self. description_en.blank?
self. description_en=nil
end
if self. description_de.blank?
self. description_de=nil
end
end

I’m so bad with metaprogramming, can’t figure out how to automatize such thing in the plugin, could you help ?

and… do you think what I’m doing makes sense ?

kind regards

It works great when a few columns need to be translated to a couple of languages. However, when many languages are required (20+) for most columns, this approach no longer scales.

Hans

BTW,
if you want to use Goldberg with translatable_columns you got to copy the two lines in init.rb into Goldbergs init.rb to initialize translatable_columns before Goldberg startup.

I’m trying to use translatable_columns to internationalize a Goldberg application. I started with the content_pages and Goldberg gets confused with saving pages.
Another problem arises from Goldberg using find_by_sql in some places which seems not to be supported. Is there a simple way out or have I to go with the nasty workaround of inserting a translation in the sql string?

Hans

You can also put some conditions around it:

class User < ActiveRecord:Base
  if column_names.include?("title_en")
    translatable_columns :title
    validates_translation_of :title
  end
  # .......
end

Thanks