Does Taxonomy List support translations of Terms by i18n ?

Hi,

I tried a LOT ot things, and I got something that seems ok, but only for le Terms names.

I post it here, in cas it may help (comment on top about my modification).

Hi,

I tried a LOT ot things, and I got something that seems ok, but only for le Terms names.

I post it here, in cas it may help (comment on top about my modification).

Here a little further (with descrption translated)

Patches are much better because they don't depend as much as what base you used, which in this case was pretty old.

However, I saw a comment in your file

// CwDrup changed line 411 (now 412) t($term->name) instead of $term->name on August 19 2008 LINE 339 t($vocabulary->description) and LINE 464 t(check_markup($term->description))

All three of these changes are invalid uses of the t() function. The t() function must be used on a static string, with some substitution allowed. You cannot translate variables like that.

The real problem here is that the core Taxonomy module is not properly distinguishing languages on terms. And i18n doesn't seem to help on that.

Another module had a patch to support i18ntaxonomy, so I will look and see if I can adapt that code.

ok,

thank you. I wait your next update.

Because of another issue I am looking at a big overhaul in TL. That should make the some, or all, of the problem go away.

Considering that D7 is going to require pretty much every query be changed, reducing the number of them now will be an extra benefit.

@CwDrup: Do you know if i18ntaxonomy will fix your problem? My new code does not do its own queries, but relies on the core Taxonomy module, which I would hope is intercepted by the i18n module.

Merging this in with #312250: Wish List for rewrite