Closed (fixed)
Project:
Entity Translation
Version:
7.x-1.x-dev
Component:
Base system
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
4 Jan 2012 at 14:55 UTC
Updated:
28 May 2012 at 15:05 UTC
I not really understand, how works this module. On the node creation form there is a language selector combo, and I can set the language of the node. It is ok. But if I post a comment to this node, then the comment's language is always set to English. Why? I think, if the comments are also translatable, then a language selector combo the is missing from the comment editor form, when that is contains translatable fields. At the taxonomy terms page also, I can not submit a taxonomy term on a custom language, only on the English. What will happen, if I submit a node on a non-English language, and the node is contains a user defined (autocomplete) taxonomy term reference field? What will the language of the new, user entered taxonomy terms? I think, English, but this is a wrong concept. These are bugs, or just these parts of the module is not complete?
Comments
Comment #1
plachWell, we had the idea of introducing field translation in D7 core relatively late in the develpoment cycle, hence we had no time to refactor every single bit of it to support field/entity translation at its best. When I started working on the UI (the core patch that became the base for this module), I found myself needing a way to address the fact that not every core entity type has a language property: comment language is filled with the current content language, but taxonomy terms (as users) simply have no language to be set. The idea to unify the workflow here is that entity types being able to specify a source langauge do it (nodes atm are the only ones capable to be explictly assigned a language), while the others are assumed to be entered in the default language, pretty much as string translation works in the i18n module.
However this is not an ideal solution, just a temporary hack to be able to have consistent translation handling for every entity type. There is an issue about introducing an (optional) language selector to each entity type edit form: #1280546: Introduce a language selection widget for every entity.
Comment #3
MArt commentedCould it be possible to use the UI language instead of the default language when creating if in «Multilingual settings» the «Switch interface for translating» is enabled?
Comment #4
plachNo, it would unnecessarily complicate things. We will have an explicit language widget once #1495648: Introduce entity language support is committed.
Comment #5
plach