Karen --
It sounds like this is probably a major bug in the Field and/or Field
UI system, and should be filed as an issue, perhaps with fgm's
suggestion as part of the solution?
--Jennifer
On 04/21/2011 03:16 AM, fgm wrote:
AIUI, 'und' only tells that the language for information being described is
undefined, not that is not language dependent.
There exist a standard for this: 'zxx' explicitly describes non-linguistic content. As
per BCP 47, "The 'zxx' (Non-Linguistic, Not Applicable) primary language subtag
identifies content for which a language classification is inappropriate or does not
apply."
________________________________________
De : [email protected] [[email protected]] de la part
de Karen Stevenson [[email protected]]
Date d'envoi : jeudi 21 avril 2011 11:26
À : [email protected]
Objet : [development] Translatable fields
I'm trying to sort out how our fields are/should be handling translation in D7.
I have date fields, which should not be translatable, being marked as
translatable. I have been digging through the code to figure out how I can
force them to not be translatable.
The Field crud has a setting called 'translatable', which defaults to FALSE,
but the Field UI sets translatable to TRUE for every field created in the UI.
There is no place in the core UI to set a default for translatability in the
field info and I can't see any way other than blunt force altering the data to
change the behavior of a field created in the UI to keep it from being
translated.
I am running into problems now where Views are broken because I tried to create
untranslatable fields (using 'und') while new fields use the site default
language instead of 'und', and the language column is getting joined into the
view because the field is 'translatable'.
I see from a few blog posts, like http://randyfay.com/node/88, that we are
recommending that people install the Entity Translation module to allow them to
identify fields to translate, but it appears that anyone who does not have that
module enabled (i.e. a core install) will end up with all fields marked as
translatable and the language value for the field populated with the site
language.
I guess I have to just leave date fields alone and go with the flow, assume
they are all translatable even if I don't want them to be. But I'm wondering if
anyone has any other ideas for how to handle this in D7.
--
Jennifer Hodgdon * Poplar ProductivityWare
www.poplarware.com
Drupal web sites and custom Drupal modules
