Comments

We just ran into an almost similar issue when missing an argument title (%1) to display translated although i18nstrings (term localization) was defined.

It seems either a handler needs to be implemented as suggested -- with the issue that handlers with different extensions are incompatible due to mutual overrides -- or we need to reimplement the title handling to correct it.

Pity, both seems hackish to me regarding clean further extensibility.

In our project we finally set the title in the theming layer. If we can't find a clean solution, even the ugliest solution is good enough ;-)

Hi miro_dietiker,
I talked to dereine today on mirc...so yea I have absolutely no justifiable reason for doing it the way I did, I'm reattaching my attempt this time with overriding the taxonomy term validator.

As of my quick thoughts:
You should try to localize terms only if the vocabulary is in LOCALIZE mode. Deactivate i18nstrings() calls in all other cases.
In TRANSLATE case you should apply language condition in the (sql) lookup to match the current language.

Load the vocabulary mode using the views settings (with given vid) and check for it.

HI!
using views and i18nviews 3.x-dev latest versions here.
I have my taxonomy set as TRANSLATE case and the argument gets translated correctly only with default taxonomy path (taxonomy/term).
When I override the vocab path with taxonomy_redirect, the argument doesn't translate.

other taxonomy related modules, namely taxonomy menu, respond correctly and change accordingly with the language; it seems that the translation of the views argument is somehow tied to the default taxonomy/term path.

I am now about to test the suggestions from this thread in order to solve my problem
I also need to check if the depth modifier may be related to this.

@miro_dietiker,
I tried a different approach, i limited the vocabs only the the ones that have been localised.
Using the filter that comes with views basically takes care of the second option unless there is something that I'm missing screenshots and patch attached.

@benklocek,
I didn't check for term id in my patch because I figured "hey we already have the id"...but maybe I should...

@bohz
I'm sorry I have no clue, I haven't used views 3 yet.

I still have to run it through coder.
I only checked with node listings, should this work for term listings as well?

Ok, I just noticed that argument translation is only not working with argument "Term ID (with depth)".
The basic argument Term ID translation works.
Could you please check this and also make it compatible to "term ID (with depth)"?