Hi,

I'm testing this module on the pretty recent drupal 6.2, and I'm enjoying to see that it is very usable for a non final relase, thanks to maintainer and contributors.

However, there is a thing that I would see about meta for terms.

With the new drupal 6 and i18n, you can choose 2 options for term translation :

  • Localize terms. Terms are common for all languages but their name and description may be localized.
  • Per language terms. Different terms will be allowed for each language and they can be translated.

the first choice is new compared to drupal 5, and, in my opinion, is far better. Creating a new term for each language was a heavy task that brings problems to a lots of taxonomy related modules because the link between the terms whan you switch language was not always made... Creating an only one term in the "master" language and translate them with locale is a very good idea.

The problem is that meta keyword is not aware about this configuration. So if you want translated meta too, you have to choose the second option.

It is possible to provide translatable meta via the locale module, as taxonomy provide terms name and description translation ?

(PS : Don't know if it's a meta keyword or an i18n issue... sorry if it's in the wrong place).

Comments

eu.claudio’s picture

subscribe

avpaderno’s picture

Category: support » feature
Status: Active » Postponed

This seems more a feature request, than a support request.
I will think about integration with i18n.module.

srobert72’s picture

avpaderno’s picture

Actually, it is. The issues refers to two different branches that are developed from two different people; that is why I am keeping them separated.

avpaderno’s picture

Status: Postponed » Closed (won't fix)

Branch 6.x-2 has never been supported, and it is not anymore developed.