Translations and multilingual Entityform Types

Not ruling this out there are just other things I would like to address first.

I know there is some discussion about how entity property translations(not fields) should be stored in general in Drupal 7 and 8. If someone wants to post some links to any of the relevant issues in either core or the Entity API modlue that would be appreciated. I would rather wait and watch some of those issues and see if there is a consensus on best practices and/or changes in core related to this.

Postponing for now but please feel free to post relevant links/issues here.

Are the field labels translatable now?
I find the field labels with admin/config/regional/translate/translate but the labels always show the original ones.

Or is this also postponed?

It seems you can field labels with the Field Translation module but I haven't tried. This should really be entity agnostic so it should work with any fieldable entity.

this is what i have running. But field translation is about the content of those fields. So the submissions....
I just need to translate the labels.

@betz,
I just tested this out to confirm I could change the labels of the fields on the form.

If you go to this path "admin/config/regional/translate/translate" then you can search for the label of the string.

@tedbow yes, could find them and translate them, but on the form nothing changed.

Ok so it sounds like you are not having it be activated. Is it working for you with node field labels?

You may need to enable a method here: admin/config/regional/language/configure

Otherwise you might need to file an issue with i18n.

You can read the docs here: http://drupal.org/node/133977

Hey,

I don´t use Field Translation. In my case field labels are NOT displayed translated. Although they are translated correctly.
I appled the patch http://drupal.org/node/1904368#comment-7079456 with no luck.
"Normal" node field label translations are displayed fine. It seems to be an issue of entityforms.

Marking this as a feature for 2.x

I've been considering how best to work on this recently, and I wanted to share some of my thoughts. If we can agree on a direction, I'd be happy to do some work on it.

For the field labels, it seems like i18n_field provides what is necessary for translating them on the form.

For the entity type properties (intro text, etc), I couldn't find an example from Entity API but I was considering the approach that taxonomies take - Vocabularies (which are bundles for Terms) are entities themselves, and thus can have fields that can be translated. Would it make sense to make the Entityform Type an entity itself and use fields to provide for translation?

@ottawadeveloper check out this issue: #1848018: Add i18n support for Label and other property translation (+ entityform name)

It is more up-to-date and has info about a branch where I have started to work on it.

I suggest to close this bug report as duplicate of #1848018: Add i18n support for Label and other property translation (+ entityform name).

Good point.

Closed. Duplicate of #1848018: Add i18n support for Label and other property translation (+ entityform name)