Tag groups localization

Adam Gitin asked on December 22, 2014 13:35

Hi,

Would like to hear how others are handling "Tag Group" localization?

We have a site with a few cultures. Each site has a blog and we would like them to share

tag group but each culture should have there translated tag name.

any ideas?

Recent Answers


Rui Wang answered on December 22, 2014 17:46

Hi Adam Tag Group it self can be localized, but the tags cannot be localized. So if you want to have language depended tags for each culture, the better solution is to create separated tag groups for each culture.

0 votesVote for this answer Mark as a Correct answer

Adam Gitin answered on December 23, 2014 06:46

" Tag Group it self can be localized," - What do you mean by this?

0 votesVote for this answer Mark as a Correct answer

Rui Wang answered on December 23, 2014 16:30

Tag Group name is like a resource string, which can be localized.

0 votesVote for this answer Mark as a Correct answer

Roman Hutnyk answered on December 23, 2014 17:03

You can create localization string in different languages and put localization macro ({$key$}) in the Page tags field. System resolves those macro according to selected culture.

0 votesVote for this answer Mark as a Correct answer

Adam Gitin answered on December 23, 2014 18:48

Thanks Roman,

I tired what you suggested: Image Text

and click SAVE.

In the tag SELECT popup I do see the actual text and not the key, but if I try use the SELECT

to remove/add tags, all tags disappear.

I also tried changing culture and selecting tags, does not work.

Does this work for you?

0 votesVote for this answer Mark as a Correct answer

Rui Wang answered on December 24, 2014 15:27

macro would make this work, but it's not going to be something the regular content editor can handle. and as you can experienced, the UI doesn't support it when you use SELECT button.

1 votesVote for this answer Mark as a Correct answer

Alexander Kontsevoy answered on January 15, 2015 10:18

Dear Adam. I use next algorithm of tags localization:

(For example we have two language cultures on the site English and Poland.)

  1. Create two different tag groups. One with name "Eng Tags" and second with "Poland tags"
  2. When you create page in another language culture, you will to have ability to select appropriate tag group in "Metadata - Tags - Page tag group" property.
  3. Place tag cloud web-part on your page.
  4. Open properties window of this part
  5. Go to "Tag Filter" section and place next macro in the "Tag group name" field

{% if (CurrentCulture == "EN-US") { "Eng Tags" } else { "Poland tags" } #%}

This is decision gives you more clear management with tags.

0 votesVote for this answer Mark as a Correct answer

Adam Gitin answered on January 15, 2015 10:50

Hi Alexander,

What you suggested is almost what I did.

This is what I did:

1) Created several TAG GROUPS, all with same group name + culture code ( tagName_en-us etc.).

2) on BLOG main page- > metadata -> selected "Page tag group" for this culture.

3) ALL blog post INHERIT that tag group

4) cusotm webpart properties using TAGs ->

-> WHERE CONDITION : {% CurrentDocument.DocumentCulture #%}

-> in actual query: Where TagGroupName = N'Blog_##WHERE##'

Thanks for all your help

0 votesVote for this answer Mark as a Correct answer

Alexander Kontsevoy answered on January 15, 2015 11:21

I hope you decided your question. Anyway, thank you for your reply.

Best regards Alex

0 votesVote for this answer Mark as a Correct answer

   Please, sign in to be able to submit a new answer.