Although Profile is enabled in the Translatable entity types in /admin/config/regional/entity_translation, I don't find any way to translate the profile type label, neither in the UI, nor as a string in the translate interface.
So I guess Profile2 is not handled by i18n but could be translated via entity translation, as long as the title module can replace the entity legacy profile label field with a regular field, isn't it?
I also wonder if I have to submit a feature request in entity translation queue about the translate tab which could appear in the profile type UI.
The related issue in Profile2 is there:
http://drupal.org/node/1118362
| Comment | File | Size | Author |
|---|---|---|---|
| main_profile_manage_fields_UI_en.png | 103.61 KB | Jerome F | |
| main_profile_edit_UI_en.png | 50.47 KB | Jerome F |
Comments
Comment #1
plachThe Title module is a workaround for a core feature that did not go into D7 core, Profile 2 too. IMO it makes more sense for Profile 2 to implement Title's field replacement API: Title supports only core entities and augmenting its built-in entity info is a far more ugly solution than implementing a hook for Profile 2. Moreover we would be making a possibily unjustified exception that might lead for any module to ask to be supported. Again Title was meant to be a fix for core, contrib modules can achieve the same results by using a field as label.
Comment #2
Jerome F commentedOf course, that's right. Thank you for this sound comment and status change @plach.