Hi,

There is something that for me doesn't make much sense. I don't know if it qualifies as bug, but it is close.

When a vocabulary is set on "Per language terms" and allowing tagging. When a new term is added it is always added as language neutral. This doesn't make much sense for me. It should be associated with the language selected when the node was created/edited. This way, there is no point as choosing "per language terms" since the terms will be constantly added as neutral. Editing term by term to select the language is not an option for free tagging.

Thanks!
Tiago

Comments

tiago.gmarques’s picture

tiago.gmarques commented

On the previous comment the language of the terms should be the one on which the content was created, which is not necessarily the same as the language selected while creating the content.

I would like to focus the importance of this feature. If the vocabulary is set on "Per language terms" I am expecting the terms to be associated to languages. I know that language neutral terms should also be available, but the default should be the language on which the content was created, otherwise terms will keep getting added as neutral and show up in all languages.

bsimon’s picture

bsimon commented

There's a similar situation with menu items. If you add a new menu item from a Create Content page, the menu item's language is always set to 'all languages'. It is not set to the same language as the page you just created.

I guess that setting something to language neutral or all languages is a case of choosing the safest option initially, maybe to make sure you can see it, at least - but it's confusing when you don't expect it.

Maybe adding a warning on those content creation pages would help.

tiago.gmarques’s picture

tiago.gmarques commented

But menu items creation is something that is supposed to be made by admins only, while entering a new tag is something any user can do. Also you don't get hundreds of new menu items each week as you can get new tags.

That is why a warning is not enough. For the tags I really think it's really necessary to have the option of terms added being added as the language selected for the content.

tiago.gmarques’s picture

tiago.gmarques commented
Title: Terms not being associated any language » New terms (freetagging) added as language neutral

I have just changed the title, I think now it reflects better this issue.

Anyone has looked into this? This is still unsolved and it is something clearly lacking in the internationalization module.

hailu’s picture

hailu commented
Assigned: Unassigned » hailu

I'm going to look into this.

tiago.gmarques’s picture

tiago.gmarques commented

Thanks!

I know this is a very specific issue, but is really important for me.

When users tag content, they don't get to choose the language of the terms, neither it makes sense to do that. However, new terms will be added as language neutral and that for me is wrong in a multilanguage site.

pedropablo’s picture

pedropablo commented

As is reflected in this very related thread #355584: Taxonomy syncronization problem when "per language terms" vocabulary used, this could be very important as if synchronization is activated, when translating a node, it will override original node terms!! (as the language neutral terms will not have a language nor a translation...)

I am not sure if this is just due to language neutral freetagging, or to the way freetagging creates new terms at node creation, so I will keep both threads open, but feel free to converge them.

stella’s picture

stella commented
Issue tags: +i18n sprint
jose reyero’s picture

jose reyero commented

I see two possibilities here:
a) Add a submit callback and override the whole term creation part
b) Implement hook taxonomy, and add some logic there to set language for already created terms, maybe easier.

Also, we need to override the autocomplete callback (form_alter) to produce the right terms depending on the vocabulary.

jose reyero’s picture

jose reyero commented
Status: Active » Fixed

Done, new terms are saved now using the node's language.

However, if using localizable terms and freetagging, see notes added at the end of this page: http://drupal.org/node/313268

tiago.gmarques’s picture

tiago.gmarques commented

@Jose: The update was made on the dev version?

Thanks for the quick response to this issue. This had been troubling me for a while.

jose reyero’s picture

jose reyero commented
Status: Fixed » Closed (fixed)

Updates are always on the dev version...