i18n of facet items

Translation is not as simple as the post above. Let's define some context around this request along with the problems we are trying to solve.

Thanks for posting back with the screenshot. In terms of the search, I want to confirm that you are searching by the same string, i.e. "en" for English, you just want the display names of the Facet items to be translated. Same would be true for "Male", "Female", and the other items in the screenshot.

Thanks,
Chris

OK, cool. Unfortunately #2 is a highly discussed topic, and AFAIK there is no elegant solution for doing it right now.

Regarding #1, my personal opinion would be to write a custom module that integrates with the Internationalization module. How you would do this is implement hook_facetapi_facet_info_alter() and change the "map callback" functions to ones in your module that do the mapping using the appropriate i18n functions. I am not an expert in the i18n module by any means, but this is the avenue you would take to translate the user generated data.

Changing to a support request because the integration points are in place i18n integration is outside of the scope of the core module. Would absolutely love to have a contrib that does the integration, though.

Thanks,
Chris

Client sponsorship = awesomeness!

Respectfully marking as "won't fix" since the code should exist as another project.

For now, a simple fix could be to just wrap the t() function on the title:

Change

/**
 * Themes a facet link with an optional count.
 */
function theme_facetapi_link_inactive($variables) {
  if (!empty($variables['count'])) {
    $variables['text'] .= ' ' . theme('facetapi_count', $variables);
  }
  return theme_link($variables);
}

into

/**
 * Themes a facet link with an optional count.
 */
function theme_facetapi_link_inactive($variables) {
  $variables['text'] = t($variables['text']);
  if (!empty($variables['count'])) {
    $variables['text'] .= ' ' . theme('facetapi_count', $variables);
  }
  return theme_link($variables);
}

BarisW,

Your solution would technically work, however it is against best practices in terms of how the t() function should be used according to the guidelines at http://drupal.org/node/322729. To quote the passage in the cheat sheet:

Using dynamic values, such as t($type). Whenever you use dynamic strings to call the above functions, make sure that all possible values are already in the code elsewhere in literal form using the API. Do not translate user provided content.

The values in this field are probably user generated strings such as taxonomy terms or content types, so a different method of translation should be used.

Thanks,
Chris

Hi Chris,

I know and I agree. But in this case, it works. And because it's in a theme function, I didn't hace to hack the module.
So it's a dirty fix until there is a better solution.

Gotcha. Thanks for clarifying, and I am sure it will help someone else out.

Thanks,
Chris

I havent tried this but #10 seems to be only translating the text and not the term id. What if you are using a different term id for a facet item based on translation? For example:

tid: 1
termname: Bars

tid: 10
termname: 酒吧

Take note that the 2 terms are linked by a translation set. This means that the expected behavior for a facet in an english site will need to have a term id of 1 and a term text as "Bars" and when switched to a chinese language, the term id needs to be 10 and so will the text change to "酒吧"

subscribe
Edit: Just noticed this issue is closed :-P my bad. However I am interested in this subject.

thegreat is awesome and posted a sandbox project at http://drupal.org/sandbox/thegreat/1276796 to start work on this issue. Let's start collaborating there on how to solve this tough problem.

Based on the BarisW's code created working patch for me.

Just an update (also posted on my sandbox page).

I18n for taxonomy term facets has essentially been resolved as a result of this: http://drupal.org/node/1340858#comment-5259368. If your taxonomy has been translated/localized via i18n_taxonomy then entity_label('taxonomy_term', $tid) will return the localized term name.

As a result I'm currently not planning any further development to facetapi_i18n.

@jaanhoinatski: your patch works but if you have vocabularies term already translated you've to translate them again due to a different string context.

Moreover instead of editing theme_facetapi_link_inactive() and theme_facetapi_link_active() it could be fixed from the execute() method (from widget_links.inc), something like:

  public function execute() {
    $element = &$this->build[$this->facet['field alias']];

    // Cycle every item and translate the markup
    foreach($element as $key => $el){
      $element[$key]['#markup'] = t($element[$key]['#markup']);
    }
  [...]

Moreover in certain case probably this would not be correct, so I'm currently working on a facet based settings to enable the translation.

So with all these solutions, do you still have to translate each terms from translate interface? there is no way to use "Translate Taxonomy term" still ! ?

hello. i noticed that you suggessed many solutions!
which one is the best to integrates with facet api module? or is there any update that contains fixed issues!