By lduperval on

Hi,

I am using the drupal 6 i18n module, and I enabled taxonomy translation. I set my vocabulary to be the same terms, localized.

Normally, I expect to do this:

Enter a term in English
Switch to French pages (using language switcher)
Change the name of the term to the French translation
When I go back to my interface, I expect the terms to show up in the proper language

Instead, what happens is that at step 3, the name changes for French and English.

I've done this for other localizable items, but it doesn't seem to work for taxonomy.

What am I doing incorrectly?

Thanks,

L

⋅ Categories: Drupal 6.x

Comments

ergunk’s picture

ergunk commented

I'm not very sure if i completely understood what steps you followed; but i would like to share how to set vocabularies for translation and how to translate terms:

1. As you create a multilingual vocabulary, you should choose "Per language terms. Different terms will be allowed for each language and they can be translated." option under "Multilingual options" panel.

2. As you add terms, you should set language for that term from "Language" drop-down.

EXAMPLE:
Consider you have a vocabulary named Fruits; and you have terms i.e Apple, Peach, Cherry etc.

- You will add term "Apple" and set language as English
- You will add term "Pomme" and set language as French
- ...

3. After you added all terms for both languages, switch to vocabulary's main page. There should be a "Translation" link on upper right corner of the page(at least for Garland theme, it is there). Click Translation link.

4. On Translation page(tab) click "Create new translation" link.

5. On the next page you will see 2 seperate drop-down lists for both Languages.

5.a From English drop-down, choose "Apple"
5.b From French drop-down, choose "Pomme"
5.c Click Save button.

Translation is done for Apple-Pomme terms! Repeat steps 4-5 for other terms.


Mediasaur | http://www.mediasaur.com/en | http://twitter.com/mediasaur

Before asking for help, please read this http://slash7.com/2006/12/22/vampires/ and don't be a "Help Vampire". :)
fibie’s picture

fibie commented

Thanks for this very helpful step by step.

I have followed this and it has worked for me great but I am stuck trying to also change the vocabulary name. The terms are translated as you describe above but I also want to change the vocabulary name for both English and Indonesian translations.

Can you help?

I am using i18n 6.x-1.0 (all enabled) with drupal 6.9 core locale and content translation

dddave’s picture

dddave commented

I ran into the same problem. Although I could enter a translation in my translation table (module) no change took place. Has anyone a solution?

lduperval’s picture

lduperval commented

Hi,

I tried what you said for the terms, and it works well. What doesn't work as well is this: I translated a term, and then I created two documents, one of which is a translation of the other. I assigned the terms correctly, but when I change the term for the English document, the term for the French article disappears and vice versa.

The net effect is this: I created a view where I want to filter articles based on the term and the language. If I filter based on the language only, the filter picks up content in both languages. If I filter on language *and* term, it picks up documents in one language but not the other.

Any ideas?

Thanks,

L

lduperval’s picture

lduperval commented

It seems the problem isn't views, but translation. I remember that when using a localized vocabulary, if I changed the term for one of my stories, the translated version would automatically have its term adjusted also. Well, when using two terms (one for French and one for English) this doesn't work properly anymore. So it really looks like I have to stick with localized terms instead of "per language" terms.

Unless I don't understand this well.

L

lduperval’s picture

lduperval commented

Found it! Turns out I had to remove the synchronization of the taxonomy terms in the settings for my content types.

L

alunyov’s picture

alunyov commented

Vegetator, thanks man! That's great think!

jenifertucker’s picture

jenifertucker commented

I'm just working through this and have done steps 1 and 2. When I go back to the translation page (/admin/content/taxonomy) there is no translation tab - only List | Add vocabulary

I have multilanguage (block translation, content type translation, Internationalization, Menu translation, String translation and Taxonomy translation), as well as Locale and Content translation.

I haven't enabled syncronization this time having read lduperval's comment.

I've just upgraded from Drupal 5 to Drupal 6 this weekend and trying to figure it all out.

Many thanks,
Jenifer

judef’s picture

judef commented

Thanks vegetator Great tutorial
regards,
judef

kenzol’s picture

kenzol commented

Hello Vgerator,
I have followed all this steps at the end in my Category menu there two link one is for english other for bulgarian .
When I am on english page must have only terms in english but there was two terms on english and bulgarian version
You can see here image.
http://yfrog.com/f/j6picbhwj/
Here is vocabulary multilanguage settings
http://yfrog.com/3upic1dbj
http://yfrog.com/72pic2mij

fo you need more info write me

Ive’s picture

Ive commented

This looks like a complex way of tagging content. Is there a way to tag in one language without having to repeat the tagging in the other languages too?

sanjay128yadav’s picture

sanjay128yadav commented

Thanks for this it is very helpful. I have created a taxonomy follow these step, But when i use this taxonomy as Menu location , all terms display in all enabled languages.But i wants to display terms (In sub menu)according to language.

Please help me.

castawaybcn’s picture

castawaybcn commented

beware, Vegetator's way does not work well with cck fields (or at least it did not for me).
The steps that made it for me where:
1. Select "Localize terms..." in the vocabulary settings
2. Install (if you have not done so) the Translation Table module: http://drupal.org/project/translation_table
3. Go to admin/build/translate/table/taxonomy

There you will be able to translate all terms easily.

I hope this helps.

msteurs’s picture

msteurs commented

I am having kind of the same issue. I think it is related to this reported bug:

http://drupal.org/node/367287

The comments above make me confused. Because, when I switch off the taxonomy synchronization in the content type page, I can add two different terms to different translations, and the initial idea was still to have the taxonomy terms automatically translated.

My opinion is that if you want to have a complete synchronization (translation), the 'localized terms' option should be used, or am i wrong ?

Does anybody have a clear opinion on this ?

Thanks !

dark.o’s picture

dark.o commented

I agree with dancinbits... played now for couple of hours with this issue of translating taxonomy terms and syncing those, but that just aint right.

With "locatized terms" option I have different tax string translations when add/edit the node. If user A uses language x, and wants to add a node, that he sees taxonomy terms in the language x. If I use language y, than I see terms in language Y. Simple. Problem: when viewed, the terms are in the default language, regardless of the language selected. There must be some easy way to do this, to view them in translations according to language selected. And I would prefere this way, not having to create multiple terms for every language with their own term ID, and then syncing those etc etc.

alexbk66-’s picture

alexbk66- commented

I played with the taxonomy translation for a while and agree with castawaybcn - that's the best approach!
Use "Localize terms..." setting and Translation Table module.

sabrawy’s picture

sabrawy commented

This is a bug when i use Views based on Taxonomy not node

its get the original terms also there is no option for translation with taxonomy in views like the node

sabrawy’s picture

sabrawy commented

Guys use i18ntaxonomyviews & i18nviews these will fix this problem.

http://drupal.org/node/346028
http://drupal.org/project/i18nviews

Ive’s picture

Ive commented

thanks for the tip msm_eg

gjones’s picture

gjones commented

I found this module worked very well.
http://www.freeformsolutions.ca/en/blog/displaying-localized-taxonomy-te...

drupalfan81’s picture

drupalfan81 commented

Great Thread!

drupalfan81’s picture

drupalfan81 commented

This is a great thread and probably the best I have found with open discussion on what's the best way to deal with taxonomy in multilingual sites. There are just two many ways, and I think a good Drupal guide should be created to explain them all and how the heck to use them all with a multilingual site.

I thought I would ask this question here since you seem to all be building multilingual sites. I am trying to convert my English only site to become a multilingual site but I'm having trouble with Content Taxonomy module and doing this. I use Content Taxonomy to make CCK fields with Content Taxonomy so they are linked to their vocabulary and display their terms in dropdown menus.

This works well, but once I change the vocabulary to use the "localize terms" format and perform the translations in the translation table then when I go back to my edit/add node, it shows duplicate dropdown fields. One for the Content Taxonomy field and another which is the Vocabulary dropdown for that vocabulary. Content Taxonomy usually hides the vocabulary one, but for some reason it's not hiding this. I'm guessing it's a bug with Content taxonomy but I can't find ONE SINGLE post on the web that is talking about this. So maybe it's not a bug and I am just doing something wrong. I can't imagine with 33,000 sites using this module NOBODY is talking about it.

If I can't get this to work, I could try instead of using the "Localize terms" method I could use the language method where you add both the term in English and the term in another language and then link them. This just seems very tedious and ALOT more work. But maybe it's the only way I can use this with Content Taxonomy. Anyone know? Also which way is better...using the localize terms method or the language method where each term in that vocabulary has a language set to it?

Thanks!