Compatibility with i18n localized terms
moritzz - November 27, 2008 - 20:13
| Project: | Tagadelic |
| Version: | 6.x-1.0 |
| Component: | Code |
| Category: | support request |
| Priority: | critical |
| Assigned: | moritzz |
| Status: | won't fix |
Jump to:
Description
If I route the translation of terms through localization (not using separate terms for each language) and apply this patch, tagadelic works flawlessly on my site.
Unfortunately I could not check how to translate vocabulary names appropriately.
Do not hesitate to contact me for further assistance.
| Attachment | Size |
|---|---|
| tagadelic.module.patch | 957 bytes |
#1
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
#2
Hi there, any progress on a fix for multilanguage tagadelic? thanks!
#3
yay, patch works great! thanks so much
#4
Check this (http://drupal.org/node/584376) if you want a patch without module_exists