Language support and ‘support for WPML’ are different things.
If I get the time to look into what it would need for the two plugins to compliment each other, I will.
hi. i understand. but showing only terms by language should be an issue even when not working with WPML. why having language support if terms of other languages are shown as well?
There is a difference between the WP core i18n supporting a variety of single languages on one installation, and a plugin creating functionality for multiple languages on a single installation.
I would like WPML compatibility too. 🙂
R
(@rreisdasilvagmailcom)
My problem with languages is slightly different but since language support is being discussed here I decided not to open a new topic.
When on the glossary term list (both atoz or simple term list) I see the terms according to the different languages and everything is fine. But when I click in each of the terms I am always referred to the description in my default language, i.e., the glossary term hyperlink is directed to
something/?glossary=glossary_term
instead of
something/?glossary=glossary_term&lang=en
Is there anything I can do to prevent this behaviour?(I am using qTranslate for language support.)
I’m still not sure how to add WPML support. I’ll look at perpetuating some query args in the shortcodes. From your description above that should allow qTranslate compatibility.
There is some experimental qTranslate support in v2.3.x – let me know if it works.
As I don’t have access to WPML, I can’t add support. If you want to bring it up on their forums, I’d happily accept a patch.
R
(@rreisdasilvagmailcom)
Excellent! It works perfectly! Thanks a lot!!
WPML has certainly free licenses for those who build extend plugins
I wouldn’t be building an extension as such. Certainly not something that would need payment.
