`translation` table is not created on upgrading from core translation

Translation 2 is meant to replace the core Translation module so if it is already enabled you will find it already enabled and the translation table won't be created. We need an update function taking care of this.

I'm afraid you'll need to remove the translation record from the system table and then enable Translation 2 again.

Here is an update function creating the schema and enabling the translation_node module (the contrib version of core translation).

better title

Looks good to me. However, this update must not run on existing sites.

I'd suggest a simple if (db_table_exists('translation')) wrapper.

Here it is.

Ready to fly, IMHO. :)

Committed to HEAD. Thanks!

A new development snapshot will be available in 12 hours.