Model data translation: Use Globalize?

[furilo]

https://github.com/globalize/globalize

[jorgesancha]

I haven't used globalize but looks good. I guess that it makes sense if the goal is to make the site translatable by the users (which could be premature maybe?) - otherwise I'd just go with Rails I18n API which is really good and uses simple .yml files. Moving to globalize after shouldn't be too hard if that's what we'd decide

[furilo]

Agreed that its premature... I was thinking on how we should translate description of projects for example. For the rest as you can see I've started using the ymls. So on hold for now.

[jorgesancha]

I hadn't thought of the project translations. A way to do this for the time being would be to serialize the project descriptions on the database. Essentially, you are storing a hash that contains all the descriptions, such as:

{ :es => "Wikipedia es un proyecto que...", :en => "Wikipedia is a project..." }

In any case, if we are going to allow people to create their own projects, we can't really ask them to translate all the descriptions. We either curate this ourselves or assume for the time being that those descriptions will always be in the original language. Whatchuthink?

[furilo]

Yeah, I would not worry much for the time being (my concern was more on the side of me learning than anything else ;)

[ferblape]

We can't work on this yet, because the gem doesn't work in 4.2: globalize/globalize#393

I'll move back the issue to the Backlog.

[furilo]

Now that I'm doing #15, we clearly something like this to be able to translate category names ;)

[ferblape]

That will go with Globalize too.

I'll take a look to the progress of the issue this weekend.

On Fri, Jan 23, 2015 at 10:42 AM, Álvaro Ortiz notifications@github.com
wrote:

Now that I'm doing #15 #15,
we clearly something like this to be able to translate category names ;)

—
Reply to this email directly or view it on GitHub
#21 (comment).