This might be a Views thing -- if so, let me know and I'll move it over.

I'm running i18n-6.x-1.3 and views 6.x-3.0-alpha3. Loving my new "reset" button for exposed filters -- but it only makes a string for me to translate via admin/build/translate/search when I change the button text to something other than "Reset" (the default value). So weird!

Also, I can't figure out how to localize "Any" (- Any - or <Any>) within my exposed filter select lists.

Lastly, this is extra weird -- some strings are available for translation (at admin/build/translate/search) as "Built-in interface" and "Views" text groups. But, the translations only seem to "work" when I do them for the "Built-in interface" strings; when I do them for the "Views" strings it totally ignores me -- and, in the case of a view Footer, my original-text doesn't display anymore when I'm viewing the page-display of the view in English.

In case it's helpful, my view is currently using the "Node translation: Content negotiation" filter (although, I'm thinking of changing that to the "Current user's language" option because Content negotiation hasn't been behaving across the board for me).

Let me know if there are any additional details I can provide to help troubleshoot. Thank you!

Comments

alison’s picture

UPDATE: It seems the issue with my footer content was related to http://drupal.org/node/765310, so we can take that out of the mix...

alison’s picture

Title: Views + i18n and/or i18nstrings -- strings not available for tranlsation » Views + i18n and/or i18nstrings -- Views text group string translations not working

Another update...

- Any - has finally appeared at admin/build/translate/search (with the Built-in interface text group), and I translated it succesfully.

SO... I think at this point my problem relates to just the translated strings in the Views text group not "working" (no longer "strings not available for translation" since it seems there was just a bit of a delay). Hopefully the new title fits the issue better.

gosta100’s picture

Hello,

I am using: Internationalization 6.x-1.4 and Views 6.x-2.x-dev, and i cannot find my "" as well. Does Views 6.x-3.0-alpha3 solve the problem?

Off topic: Could I change the string "" itself?

Thank you.

alison’s picture

Hi gosta100,

I've found many strings have been very slow to appear at admin/build/translate/search -- perhaps because the Views textgroup can't be manually refreshed via admin/build/translate/refresh, I'm not sure. I've tried clearing the cache, running cron, repeating this exercise -- in effort to speed things up. I honestly don't know if any of that worked; there was still a delay, though it may have been shorter.

I do think that it's a good idea to go to admin/build/views/tools and choose - Any - instead of the default, <Any>, because i18nstrings doesn't seem to care for < >. But, again, I don't know for sure if this matters; it might just be that making the change from the default to - Any - serves as a nudge for a new translatable string to be created, and it may have nothing to do with the symbols.

Hope this helps at least a little!

(I don't think your Views version has anything to do with this -- though I think i18nviews 6.x-1.3 required views 3... I don't know if i18n-6.x-1.4 does, but you could look on admin/build/modules in the details included with the "Views translation" listing.)

Jose Reyero’s picture

Project: Internationalization » Internationalization Views
Version: 6.x-1.3 » 6.x-2.x-dev
miro_dietiker’s picture

Version: 6.x-2.x-dev » 6.x-3.x-dev
Status: Active » Closed (works as designed)

You need to use i18nview 3.x release.
The i18nviews string translation group is meanwhile working.

Since one of the most recent commits you even don't need to refresh the textgroup: On every view save, the strings are persisted / created and immediately ready for translation.

kla2t’s picture

With this configuration:

Internationalization 6.x-1.9
Views translation 6.x-3.x-dev
Views 6.x-3.0-alpha3,

the only response when "Views" has been selected for translation is:

- No strings found for your search.

Moreover, when I try to refresh strings for Views (yes I know I don't need to...), I get the fatal error message:

- Call to undefined method view::save_locale_strings() in [...]/sites/all/modules/i18nviews/i18nviews.module on line 48.

I have two languages - german and english - and apart from Views, the translation is working fine, even regarding taxonomy.

Any hints? Thanks!

kla2t’s picture

OK - upgrading to Views 6.x-3.x-dev fixed the issue for me!