Compatibility with i18n localized terms

Thank you very much for you work.

But I very much dislike if module-exists solutions. They are neither modular, nor scalable. Imagine having to make exceptions and if/elses for every single of the 400+ modules around?

IMO this should be handled in the i18ntaxonomy module. Tagadelic uses all the proper hooks and apis to render taxo terms, so if they are not translated, then either:
* tagadelic forgot to implement an api or hook somewhere: we have a bug to fix,
* i18ntaxonomy does not work with the proper tools, and should fix their bug,

Ber

yay, patch works great! thanks so much

I implemented the changes in the patch to standard 6x-1.2 release. It works perfectly. (It doesn't work for the latest .dev release of tagadelic).

The drawback is that the size of the tag is still determined by the number of nodes in the original language, rather then then number of translations in that tag. (I think that's something that should be handled by the tagadelic module)

But then there are other elements of this functionality that should be handled by the i18n Taxonomy module.

It would be nice to have a fully working solution for multilingual sites that are using tagadelic clouds for tags as translatable strings.

Hi,

I've been searching a solution to this issue, but couldn't find any so far...
It goes like this : when setting my vocabulary "blog post tags", I can choose between "Per language terms" and "localize terms".

- "Localize terms" integrates with taxonomy : the tag cloud only shows tags in the right language. Yet when choosing "localize terms", on the blog posting page, terms should only be entered in English (and this is a problem, for instance, for a user who is writing in Italian and has to translate every of his tags to English...)

- "Per language terms", on the contrary, doesn't compel users to write tags in English, so it would be great to go with that, but unfortunately it doesn't work with the Tagadelic module. The Tagadelic tag cloud then displays tags in all languages, not only in the current language.

So has you already figured out this is a common issue to tagadelic and Taxonomy, so I don't know who should handle this... (and I could not find the place to forum post for "taxonomy" since this is included in the core).

What do you think ? Would you patch fix that issue ? My last post got closed for duplicate reasons, but I'm unsure this one is about the same problem. :)

When I was using Cumulus I had the exact same issue, the tag cloud displayed all terms (regardless of language).

My solution was to extend tagadelics function tagadelic_get_weighted_tags by an additional parameter for language (defaulting to NULL). Further, the block hook has to be altered in order to call the function mentioned above with that new parameter.

Tagadelic then only loads terms of the selected language OR terms without any language set.
[I was in need of this since I had terms which where spelled the same in two languages and therefore have not been assigned to a specific language.]

I just created a patch against latest version 1.3, maybe this helps you if you have got vocabs with terms per language.

Cheers,
Paul