nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How to use only one taxonomoy to support multilanguage sites

wexio89

Hi all,

Is there a way which somehow I can use ONE taxonomy to support multilanguage sites?. In other words if I have a taxonomy written in English but I want to use the same taxonomy to suggest metatags for a French site and assign the metatag in French with the same UID and everything (instead of the english metadata), could that be possible?

Find more posts tagged with

Comments

moonkhanna

Hi all,

Is there a way which somehow I can use ONE taxonomy to support multilanguage sites?. In other words if I have a taxonomy written in English but I want to use the same taxonomy to suggest metatags for a French site and assign the metatag in French with the same UID and everything (instead of the english metadata), could that be possible?

I think, people would like to know the exact issue you are facing in doing what you want to do? Have you tried doing what you are saying and facing any issues?

wexio89

Hi Munish,

Yes the issue that I'm facing here is that the content is actually tagged with a different UID for example:

Say I have the node wood in English with a 198blabla UID, and say I have another node in Spanish for the same word called "madera" with a 209blabla UID. In this case the nodes are phisically different since they have different UIDs. The thing that I'm trying to achieve here is to be able within the Teamsite TagUI and the suggest property to tag content with the same UID node as the english term instead of tagging the content with the spanish UID term. Is that possible?

Migrateduser

Yes it is totally possible if you are doing a manual term assignment. It is not what we would recommend as a best practice though. There are different issues depending on the assignment of the labels in the vocabulary; meaning recognizer or classifier.

If it is manual (using a browse-only vocabualry):
Doing what you are describing requires that you manage the definition of the UIDs for a new node in a manual fashion. Never what we would recommend.

1. create your vocabulary
my_vocab
wood (en::a001)
madera (es::a001)
2. create a Content Processor (CP) for each language
3. enable the vocabulary for each CP
4. as a post processor remove any labels and UIs not for the target language of the CP

This is not recommended. It is VERY easy for someone not detailed oriented to make an entry in the vocabulary that does not align to the UIDs.

I would rather see you implement a solution where each CP is per language and has its own language specific vocabulary. It would mean you could leverage MT's automation of label assignment if needed in the future. Since each defined autmated vocabulary would function best when it is language specific. I understand it would mean managing UIDs across vocabularies, but in both cases you are having to manage UIDs, so why not use the method that is more flexible to new needs going forward?

wexio89

Hi mkimbrell,

I completely support your idea. Let's see what business thinks of this, thanks for your help