Translate selectlist option values in drupal 7

By rantebi on 22 Mar 2011 at 08:59 UTC

Hi,
I've added some CCK seleclist fields to my site.
They have the following allowed values:

0|Attorney
1|Associate
2|Intern

How can I translate the textual values?
In drupal 6 you had the option to write PHP code for allowed values, so in that way translation was available (For more details see http://drupal.org/node/182884#comment-280925).
But I don't see an equivalent field in drupal 7...
Neither can i find any other issues that solves this problem.

Does anybody have a clue?

Comments

I created a new formatter for the field...

rantebi commented 4 April 2011 at 14:11

After searching and posting in many blogs i found no answers. this is the solution I found:

/**
 * Implements hook_field_formatter_info().
 */
function my_module_field_formatter_info() {
  return array(
    'list_default_t' => array(
      'label' => t('Default with localization'),
      'field types' => array('list_integer', 'list_float', 'list_text', 'list_boolean'),
    ),
  );
}

/**
 * Implements hook_field_formatter_view().
 */
function my_module_field_formatter_view($entity_type, $entity, $field, $instance, $langcode, $items, $display) {
  $element = array();

  switch ($display['type']) {
    case 'list_default_t':
      $allowed_values = list_allowed_values($field);
      foreach ($items as $delta => $item) {
        if (isset($allowed_values[$item['value']])) {
          $output = t(field_filter_xss($allowed_values[$item['value']]));
        }
        else {
          // If no match was found in allowed values, fall back to the key.
          $output = t(field_filter_xss($item['value']));
        }
        $element[$delta] = array('#markup' => $output);
      }
      break;
  }

  return $element;
}

This is copied almost exactly from the list core module, I just added the t function.
Usually you better not translate with t dynamic expressions but I was a bit lazy -> does anybody have a better way?

Instructions:
1. Add this code to any of your enabled modules.
2. You would then have to select the "Default with localization" in your content-type's manage display section.
3. The terms you support in your field should be translated and imported to the translation interface under "Built-in interface".

cool.

franknecklace commented 18 February 2016 at 23:22

good post.

hook_form_alter would let you

jason.fisher commented 29 April 2011 at 06:09

hook_form_alter would let you adjust #options values less invasively. You might instead store a list of "translatable" content types as a variable, with eventual configuration with a setting on the content type itself. Then the fields could remain untouched.

The D7 version of cck module

czigor commented 1 June 2011 at 08:31

The D7 version of cck module lets you write PHP code for allowed_values, just like in D6.

Where

iongion commented 11 December 2011 at 20:14

"D7 version of cck module lets you write PHP code for allowed_values"

- where/how do you see that ?!?

Custom module

Norberto Ostallo commented 9 February 2012 at 17:12

You have to implement a hook in a custom module.

in case anyone up to this,

joetsuihk commented 9 March 2012 at 16:51

in case anyone up to this, there are two methods to provide:
1. install D7 cck module, and you have new textarea for PHP code, and also a textfield to supply a function name for that array.
2. use hook_field_info_alter, there is a allowed_values_function, you can supply that function name also

p.s. I am using first method, on cck 7.x dev 2011-Aug-23

Here it is

yul63 commented 22 May 2012 at 22:14

Took me hours to find. Though it's for Fields, it might work with CCK.

First you need to translate the values in the field form (/admin/structure/types/manage/MYNODETYPE/fields/MYFIELD/translate). Then go to "Manage display" (/admin/structure/types/manage/MYNODETYPE/display) and set the format of MYFIELD to "Default translated".

See http://drupal.org/node/1218880

Thank you

aquadrop commented 2 August 2012 at 10:48

... it worked like a charm. I was wondering why field names showed up correctly, while the values didn't.

Perfect

i.explose commented 23 August 2012 at 09:27

That made the trick. thanks!

Yul63: excellent! Simple and

yoeld commented 24 August 2012 at 13:07

Yul63: excellent! Simple and elegant. Many thanks.

Thanks a lot

dongtian commented 2 April 2014 at 15:53

It works perfect.

Thanks

mjk3r commented 16 July 2014 at 19:56

Thank you so much! You saved my day. Was going crazy over this one.....

Thanks, for this trick...

saify commented 12 August 2014 at 08:19

Thanks, for this trick...

Thanks !!

Geolim4 commented 7 August 2015 at 12:35

That's exactly what i need, thanks my savior !!

Thank you so much!

ivincent89 commented 3 December 2015 at 08:07

Thank you so much! it works really well...

You are my hero. Thank you so

sirmanux commented 19 July 2016 at 12:22

You are my hero. Thank you so much.

help

seeem commented 30 July 2016 at 12:40

guys i did every thing but still not working !!! the list still in english !!
any idea ?
by the way the select list in search views ,,,,

worked great for me. Thanks!

memoday commented 20 February 2017 at 05:07

worked great for me. Thanks!

views

frazac commented 23 October 2014 at 08:11

wow thanks. but don't work for translate dropdowns in the exposed filters in the views. any further idea? tks

This is what you need:https:/

Marcus_Johansson commented 18 May 2015 at 16:01

This is what you need:
https://www.drupal.org/project/i18nviews

big thanks

david852 commented 1 April 2016 at 05:13

Even years later this article still does a wonderful job of giving someone new to Drupal Translations a good overview of the pro's con's between these two approaches!

Thank you!!

steps for how to translate the select list

seeem commented 3 August 2016 at 11:53

hello guys i found the solution for how to translate a select list in a views after a lot of searching follow this steps and i hope that's will work
step 1: translate the select list in (structure/content types/Manage fields) and translate the options there.
step 2: go to (structure/content types/Manage display)and change the format for the select list from default to default translated .
step 3: go to the view and change the old content in FILTER CRITERIA to the new content the translated one .

by this steps the select list will be translate ;)

Thank you

andey12345 commented 29 September 2016 at 09:38

Thank you very much)

U welcome my friend ;)

seeem commented 29 September 2016 at 09:58

U welcome my friend ;)

Do not use t() for dynamic strings, use i18n module

TwoD

Swedish

Sweden

commented 6 October 2016 at 07:44

Look at how i18n_field_field_formatter_view() checks if there is a translation function available before falling back to printing out the untranslated list. (This function first checks to see if the 'Default Translated" formatter has been selected. If you always want translated strings, skip that part.)

For facets you could use the

scuba_fly

Netherlands, Vinkeveen

commented 28 February 2017 at 09:12

For facets you could use the hook_facet_items_alter.

Goto your facet configuration, check the box "Rewrite facet items via callback function" as active filter and in the filter settings.

Then implement the hook in your module:

function HOOK_facet_items_alter(&$build, &$settings) {
  if ($settings->facet == "YOUR_FACET_NAME") {
    foreach($build as $key => $item) {
      $build[$key]["#markup"] = t($item["#markup"]);
    }
  }
}

Freelance Drupal developer, contact me if you want help on your Drupal project.

allowed values translation

pauln600 commented 1 May 2017 at 19:12

I have a content type set to French but the allowed values on the field select lists are actually English. I'd like to define the field to be French and translate the field values (it's not important that the original values are in English, they will never be displayed). But in the translate interface the English field values are assumed to be French. Any way of setting the field language to English so the French values can be created?