Hi,
I have a list field that I have translated. Everywhere when I can display this field, I have a choice of showing the "By default" or "Default translated". I always chose "Default translated" as much as it's not an intuitive wording it work.
However, when using the Grouping field found in FORMAT -> Format -> Setting (or "Paramètres" in French) although the format of the output is exactly what I want, the text is never translated. I guess it have to do with the choice of "By default" or "Default translated" I have everywhere else for that kind of field.
Is there a way to chose "By default" or "Default translated", or a way to hardcode this by default to "Default translated" when we have a text list field (and other if this apply too to them).
Thanks :)
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | groupedViews.png | 64.83 KB | sharky999 |
Comments
Comment #1
merlinofchaos commentedThe setting you speak of (By Default?) is not a setting of Views. I presume i18n is adding it somehow?
Because of that, I don't really know that I can offer much advice about its usage.
Comment #2
dawehnerCan you show us an export of your view and perhaps even a screenshot?
Comment #3
sharky999 commentedHere is the export of the view. Below, I have some explaination.
So, as you can see, I'm grouping node the display with a field named field_partner_kind.
$handler->display->display_options['style_options']['grouping'] = 'field_partner_kind';Some line below, you see that I have also that field setted for display the translated label. This is the line showing this.
$handler->display->display_options['fields']['field_partner_kind']['type'] = 'i18n_list_default';When using the setting "By default" (see screenshot), that line disappear, and when using "By key", this line is now like that:
$handler->display->display_options['fields']['field_partner_kind']['type'] = 'list_key';I'm leaving postponed for more information. It might need to be move to i18n project, if you think so viewing the current information.
Comment #4
dawehnerThis seems to be a i18n question.
Comment #5
sharky999 commentedI'm removing postponed for more information since it has moved to i18n and I think there is enough information for i18n to get the idea of the bug. If you need more information, please tell me.
Thanks :)
Comment #6
sharky999 commentedIt seems to be related to those tickets too:
#1175802: Support for field groups?
#1107152: fieldgroup label translatable