Return to Answer

Instead of copying the content of the field you can try the Entity Translation module and only make some fields translatable. It will be much less messy than any kind of copying, where you'll end up with 2 or more copies of data that should actually just be one piece of data.

If you enable Entity Translation on your site you shouldn't enable Translation for this Address field, but you should enable it for other fields that you want to be translated.

Allows (fieldable) entities to be translated into different languages, by introducing entity/field translation for the new translatable fields capability in Drupal 7. Maintained by the Drupal core i18n team.

 

This project does not replace the Internationalization project, which focuses on enabling a full multilingual workflow for site admins/builders. Some features, e.g. content language negotiation or taxonomy translation, might overlap but most of them are unrelated.

I'm using this on a multilingual website. I don't want the product status field to be translatable:

But the body should be translatable:

Instead of copying the content of the field you can try the Entity Translation module and only make some fields translatable. It will be much less messy than any kind of copying, where you'll end up with 2 or more copies of data that should actually just be one piece of data.

If you enable Entity Translation on your site you shouldn't enable Translation for this Address field, but you should enable it for other fields that you want to be translated.

Allows (fieldable) entities to be translated into different languages, by introducing entity/field translation for the new translatable fields capability in Drupal 7. Maintained by the Drupal core i18n team.

This project does not replace the Internationalization project, which focuses on enabling a full multilingual workflow for site admins/builders. Some features, e.g. content language negotiation or taxonomy translation, might overlap but most of them are unrelated.

I'm using this on a multilingual website. I don't want the product status field to be translatable:

But the body should be translatable:

You can try the Entity Translation module and only make some fields translatable. So if you enable Entity Translation you shouldn't enable Translation for this field, but you should enable it for other fields.

Allows (fieldable) entities to be translated into different languages, by introducing entity/field translation for the new translatable fields capability in Drupal 7. Maintained by the Drupal core i18n team.

This project does not replace the Internationalization project, which focuses on enabling a full multilingual workflow for site admins/builders. Some features, e.g. content language negotiation or taxonomy translation, might overlap but most of them are unrelated.

I'm using this on a multilingual website. I don't want the product status field to be translatable:

But the body should be translatable:

Instead of copying the content of the field you can try the Entity Translation module and only make some fields translatable. It will be much less messy than any kind of copying, where you'll end up with 2 or more copies of data that should actually just be one piece of data.

If you enable Entity Translation on your site you shouldn't enable Translation for this Address field, but you should enable it for other fields that you want to be translated.

Allows (fieldable) entities to be translated into different languages, by introducing entity/field translation for the new translatable fields capability in Drupal 7. Maintained by the Drupal core i18n team.

This project does not replace the Internationalization project, which focuses on enabling a full multilingual workflow for site admins/builders. Some features, e.g. content language negotiation or taxonomy translation, might overlap but most of them are unrelated.

I'm using this on a multilingual website. I don't want the product status field to be translatable:

But the body should be translatable:

You can try the Entity Translation module and only make some fields translatable.

Allows (fieldable) entities to be translated into different languages, by introducing entity/field translation for the new translatable fields capability in Drupal 7. Maintained by the Drupal core i18n team.

This project does not replace the Internationalization project, which focuses on enabling a full multilingual workflow for site admins/builders. Some features, e.g. content language negotiation or taxonomy translation, might overlap but most of them are unrelated.

You can try the Entity Translation module and only make some fields translatable. So if you enable Entity Translation you shouldn't enable Translation for this field, but you should enable it for other fields.

Allows (fieldable) entities to be translated into different languages, by introducing entity/field translation for the new translatable fields capability in Drupal 7. Maintained by the Drupal core i18n team.

This project does not replace the Internationalization project, which focuses on enabling a full multilingual workflow for site admins/builders. Some features, e.g. content language negotiation or taxonomy translation, might overlap but most of them are unrelated.

I'm using this on a multilingual website. I don't want the product status field to be translatable:

But the body should be translatable: