Hello,

I'm using TMGMT and it's mostly working fine on my content type.
But I've got several fields that I don't want to be translated.
If I click on this field in my content type setting, I see:

Field translationAll occurrences of this field are untranslatable:
    Field in Content Type
Enable translation

but if I run a translation with for instance MS translator plugin, it is being translated anyway.
How can I stop this?

(Not sure whether this is a bug or a feature or a mistake behind the keyboard?)

Thanks,
Transmitter

Comments

miro_dietiker’s picture

miro_dietiker
Location Switzerland
commented

If a field is not translatable, how could a translation be stored?!

I guess you have an invalid mixed setup of both content translation (where the whole node gets duplicated and all fields are "translatable" and entity/field translation enabled at the same time. Those are two different core concepts.

transmitter’s picture

transmitter commented

Probably right .. which modules am I supposed to use or not to use?
My node get's duplicated - that is correct and I want it to be like this.
But TMGMT shouldn't provide the fields for translation that I don't want to be translated.

I've got:
Field translation
(i18n_field)
Off

Entity Translation
(entity_translation)
On

Internationalization
(i18n)
On

Is that setup still ok?
Can I get my desired outcome working in a different way?

cgalli’s picture

cgalli commented

Hi there

the modules are not the central issue here. The way you choose to translate your content types is the matter at hand.

In the publishing options of your content type you can choose between node translation and field translation. When choosing field translation, you can set the translation option for every field in the content type (to be found in the field specs, at the bottom).

There is probably a mix up of both in your content type. Try resetting everything and use field translation only. Do NOT activate the translation option on reference fields .

Then tmgmt (as well as manual translation) will leave the reference content alone.

miro_dietiker’s picture

miro_dietiker
Location Switzerland
commented

With content translation (leading to node "duplicates" as described), you can use i18nsync to force fields being identical on all instances. However as far as i know if you use content translation, all fields are considered multilingual (they actually are) and all are part of the TMGMT job.

Improving content translation is a task that needs a lot of code / time.
Since field translation is the future (Drupal 8) this is where we focus for features.
Patches with test coverage are always welcome.

miro_dietiker’s picture

miro_dietiker
Location Switzerland
commented
Category: Bug report » Support request