Hello,
I just came to a problem where I asked myself about the definition of field labels and taxonomy terms. At the moment a field label / taxonomy term as I understand is handled as interface component and can be translated as such.
But there is some drawback in this handling. If I split the language detection to have the interface language selected by user setting and the content selection by url I will never get the right labels to my fields in frontend views because the interface language is different from content.
Example:
I have a content type 'office' set to 'Multilingual enabled' with a term reference 'country' and different translated country names. My site languages are english and german.
The interface language detection is set to user to have the user work always in his language environment while the content detection is set to url to present always content in the requested language.
In this scenario I will not get displayed the correct translations for labels and taxonomy terms but always the interface language. This is not the right thing for frontend display of nodes. When in view mode the labels and terms should be translated to content display language.
I think there should be a difference in creating / updating content and viewing content because vice versa when I edit content I need labels and terms translated by interface language and not url detected language.
Do I make a wrong conclusion here by misconfiguring my site or do I need my users to live with interface language switching problems if I want correct viewing languages?
Comments
Comment #1
rogerpfaffI moved this issue ti entity translation because this module provides the functionality to separate the settings for UI and content.
Comment #2
kristen polI'm not sure I understand how you have things configured but you can:
* use the Internationalization package's Field translation module to translate field labels/descriptions
* use the Internationalization package's Taxonomy translation module to translate terms
So, you can get both the label and the terms to show up in another language if you make sure to translate the field labels and the terms.
I'm not sure if this is what you are describing or not though so feel free to add more clarification.
Good luck,
Kristen
Comment #3
kristen polComment #4
plachI suppose this is fixed.
Comment #5
rogerpfaffI leave this as fixed for the automatic close. Currently I'm not able to rebuild the settings that led to this situation. Currently everything works within normal and logic.
Comment #6
kristen polComment #7
XmhO commentedI'm sorry but I don't think this should be closed at all.
Indeed, if you have a taxonomy that is configured to translate each term ("Translate" option in the vocabulary) and that you have :
- a content "A" in french for example,
- a content "B" in german,
- the content type with a term reference to a translated term,
When you create the content A, setting "X" as the referenced term, and that you create the translated content "B" with the translated term of X as its own term, and if you then go in the content admin page in german interface for example in order to edit the FRENCH content, you won't see any term associated with the french content, because the french content's tag is FRENCH whereas taxonomy field is rendered based on the interface language (German).
To me, when you browse a content via the admin page in french language for example, you should see taxonomy's field with german language if the CONTENT is in german language. It seems logical.
Another solution would be to switch, in this case, the administrator from the german interface to the german interface automatically in order him to see the proper tags. I don't know if It is possible?