Question 1

How to add translations to an existing Rails model with Globalize?

Accepted Answer

First, declare translatable attributes in the model with `translates`, then create a migration using `Post.create_translation_table!` with `migrate_data: true` to move existing data. Remember to remove original columns after migration if desired.

Question 2

Globalize vs Mobility for Rails model translations?

Accepted Answer

Globalize is simpler and more integrated with ActiveRecord conventions, ideal for straightforward translation table needs. Mobility is more flexible with multiple storage strategies and actively maintained, but has a steeper learning curve. Choose Globalize for legacy compatibility, Mobility for new projects.

Question 3

Does Globalize support fallbacks for blank translations?

Accepted Answer

Yes, by adding `fallbacks_for_empty_translations: true` to the `translates` method, it will use fallback locales when translations are empty strings or nil, not just when missing. This relies on Rails' I18n fallback configuration.

Question 4

How to filter records that have translations in a specific language?

Accepted Answer

Use the `with_translations` scope, e.g., `Post.with_translations('en')`, which returns only records with existing translations for that locale. This is useful for displaying content available in a user's language.

Question 5

What are common issues when setting up Globalize migrations?

Accepted Answer

A known issue is PostgreSQL not-null constraint errors; the workaround is to remove constraints from translation columns. Also, migrations must use `reversible` blocks and cannot be in the `change` method, adding complexity.

Question 6

Can Globalize handle dynamic content in translated strings?

Accepted Answer

Yes, it supports interpolation similar to Rails I18n, allowing placeholders like `%{variable}` in translations. Access them by passing a hash to the attribute method, e.g., `post.title(superlative: 'rocks')`.

Question 7

Is Globalize thread-safe in production?

Accepted Answer

Yes, it uses the request_store gem to manage thread-local variables, ensuring thread safety in Rails applications. For non-Rails setups, manual configuration of RequestStore is required as per its README.

globalize

What is globalize?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions