Hi,

Somehow using newest .dev views doesn't translate any views-field with string translation anymore.
May be this is related to http://drupal.org/node/1008358 and Internationalization Views needs to adjust to this.

First I had a views instance of 6.x-3.x-dev (2010-Jul-11) together with latest dev. Internationalization 6.x-1.x-dev (2011-Mrt-19) and Internationalization Views 6.x-3.x-dev (2011-Mei-13).
Then "Node: Link" "Text to display" was translated and not the "Taxonomie: All terms" field.
The node body itself is nicely language depended.

Now I have the views instance of Views 6.x-3.x-dev (2011-Jun-02) with http://drupal.org/node/1008358 inside.
Then "Node: Link" "Text to display" is NOT anymore translated and the "Taxonomie: All terms"field is also still not translated. The node body itself is again nicely language depended shown.

Somehow the views fields which are translated through string translation are not translated anymore with latest dev versions.

Thanks a lot in advance for your reply.
greetings, Martijn

Comments

Summit’s picture

Status: Active » Fixed

Hi,
I was incorrect to assume that the newest update of views changed the interface between Internationalization Views and Views. I needed to add more translation strings after the newest views update, now the "Node: Link" "Text to display" is correctly translated.

The terms in the "Taxonomie: All terms" field are still not translated correctly, but for that there is another issue: http://drupal.org/node/845616.

Sorry to disturb you with this issue.
Greetings,
Martijn

Summit’s picture

New update. Taxonomie: All terms are translated nicely, if you are able to get the translation of the terms in your country locale database. I had to go to [website]admin/build/translate/refresh
and refresh my vocabulary, before the terms where available for string translation.
Now they are working fine!

greetings,
Martijn

miro_dietiker’s picture

That's for the case localized vocabulary.
And the string refresh is a i18n_taxonomy issue.

The taxonomy translation itself come from i18n_taxonomy.
The module i18nviews only triggers its translation inside of views - because i18n_taxonomy only supports core elements / core display variants.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.