Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Why do you think this solution is outdated? #2

Open
jensb opened this issue Aug 8, 2011 · 3 comments
Open

Why do you think this solution is outdated? #2

jensb opened this issue Aug 8, 2011 · 3 comments

Comments

@jensb
Copy link

jensb commented Aug 8, 2011

Hello,

on your blog where you introduce translateable_columns, you also mention that you think this solution is outdated.
I am in the process of internationalizing a Rails 3 application where about 50 tables contain translatable columns, and I like your solution a lot, better than Globalize3's solution of creating a second table for each translatable table.

What alternatives are there to your solution? Does this not work in Rails 3 any more?

Thanks,
Jens

@iain
Copy link
Owner

iain commented Aug 11, 2011

Well, I haven't touched it since 2008 and have no plans on maintaining it. If you want to maintain it, you're more than welcome!

@jensb
Copy link
Author

jensb commented Sep 7, 2011

I am using in a Rails 3 app and so far, it works fine. I'll fork it when I find bugs. Thanks!

@henrik
Copy link

henrik commented Mar 16, 2012

I made a new lib inspired by this one: https://github.com/barsoom/traco

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants