Localization of taxonomies: what is possible today?

[steven-spits-servico]

Yes, another topic on localization of taxonomies. And yes, I have read all previous topics, like #4845 en #11070, so I understand it's a difficult thing to implement.

An ideal solution would be to have term localizations, but all attempts were abandoned. So I don't see this happen in the near future.

So that leaves localization of taxonomies, which is possible today, correct?

I see two problems with this approach:

• The TaxonomyField only allows one taxonomy, so users will see for example the English terms when creating a French content item. No ideal, but no showstopper.
• How do you relate 'translated' terms to each other to show the correct translation to users on the frontend?

Any guidance on what works (and what doesn't) is much appreciated. I need to implement this for a client and I'm looking for a viable solution.

[steven-spits-servico]

@hishamco Saw your https://www.youtube.com/watch?v=WQbpRHV9ugw video. Have you ever tried taxonomy localization?

[hishamco]

Unfortunately not much, it seems @urbanit is the guy who is interested in this if I remember correctly. I might look to the issue

[urbanit]

Hey @steven-spits-servico ! I hope you are fine!
There is no merged solution apparently :-(

The TaxonomyField only allows one taxonomy, so users will see for example the English terms when creating a French content item. No ideal, but no showstopper.
The one that I followed here: #6316 is a good start but no completed... That's why it wasn't merged but closed. I used this approach in order to load in editor terms that their parent taxonomy has same locale as the content item.

How do you relate 'translated' terms to each other to show the correct translation to users on the frontend?
In order to synch terms, we used the same alias for them across localized taxonomies.. we have added Alias part in terms and make the term-a-en under taxonomy A(En) and term-a-fr under taxonomy A(Fr) to have the same alias "term-a".

[urbanit]

And apparently sorry for the late response

[steven-spits-servico]

Hi @urbanit, thanks for your insight on this issue.

Am I correct to assume localizing terms is something that will never happen in OC, (at least not anytime soon), as all efforts try to make localized taxonomies work correctly? @sebastienros, care to share your point of view on this?

Our particular case:
See https://www.caractere.be/nl/zoeken?land=griekenland. Most filters on the left are taxonomy terms . Client asked us to add English and French to the website.

[sebastienros]

I don't remember the details. What I know is that each language will usually have it's own taxonomy, meaning different terms. So you can't have a 1-1 mapping of terms between taxonomies, and find the corresponding one from the other taxonomy's localization.

I believe the current option is to tag content items with terms coming from multiple taxonomies, each term from each language. Would that work?

In your case you will probably say that all these terms would have a matching entry in each language, so you would be fine with having each term be localizable, and a single taxonomy content item. Maybe that could be a fine assumption to allow term to have the localization part.

[BenedekFarkas]

For inspiration: Orchard 1.x has this figured out, in large part thanks to the hard work of the Laser team who invested heavily into localization. The last half hour of my Harvest 2017 talk covers the then-ongoing developments and here are the mentioned design notes: OrchardCMS/Orchard#7352