<p>I can confirm this is indeed the case (as of  2.1.2564). I don't know if it's intended behaviour or a bug, but I would wager the former.  I seem to recall somewhere learning that P&amp;T made an explicit decision to not have tag Names be translatable.</p>

<p>As a workaround you could consider a tag custom field with a "translatable label" that you fill in for each language? Seems a bit lame. I'd probably opt for simply making the field itself translatable, and then binding separate tags for each language.</p>

CC BY-SA 3.0
2014-07-23T12:15:43.383Z
Thanks John. I'll probably go in the direction of creating separate tags for each language.
Adam Snetman
CC BY-SA 3.0
2014-07-22T19:31:29.107Z
2014-07-22T19:31:29.107Z
John D Wells
<p>I'm building a multi-lingual site (english and spanish) and I have a news section with entries that have a "tags" field attached.</p>

<p>I've marked this field as "translatable" in the CP.</p>

<p>But, when I've added a tag to an entry, double clicking it reveals the pop-up field editor where I can switch between locales as expected (see screenshot). But I can't enter different values for "Name" in each locale. It behaves like a  non-translatable field where changing the value in one locale changes it for all the others.</p>

<p><img src="https://i.sstatic.net/ScyQ4.png" alt="enter image description here"></p>

<p>Setting my "tags" field as translatable in the CP seems to allow me to assign different tags to the entry for each locale, but that's not what I want. What I want is to have an entry's tags persist across locales, but be translated into their appropriate language.</p>

<p>Is the default "Name" field for tags translatable? How should I be setting this up to get the behavior I want?</p>

<p>Thanks for the help.</p>

<localization><tags>
Problems translating the default "Name" field on tags
# Problems translating the default "Name" field on tags

(Asked by: username_0 on 2014-07-22)

I'm building a multi-lingual site (english and spanish) and I have a news section with entries that have a "tags" field attached.

I've marked this field as "translatable" in the CP.

But, when I've added a tag to an entry, double clicking it reveals the pop-up field editor where I can switch between locales as expected (see screenshot). But I can't enter different values for "Name" in each locale. It behaves like a non-translatable field where changing the value in one locale changes it for all the others.

![enter image description here](https://i.sstatic.net/ScyQ4.png)

Setting my "tags" field as translatable in the CP seems to allow me to assign different tags to the entry for each locale, but that's not what I want. What I want is to have an entry's tags persist across locales, but be translated into their appropriate language.

Is the default "Name" field for tags translatable? How should I be setting this up to get the behavior I want?

Thanks for the help.

**Tags:** localization, tags

---

## 1 answers

### Answer by username_1 on 2014-07-22. Score: 2 | Accepted answer

I can confirm this is indeed the case (as of 2.1.2564). I don't know if it's intended behaviour or a bug, but I would wager the former. I seem to recall somewhere learning that P&T made an explicit decision to not have tag Names be translatable.

As a workaround you could consider a tag custom field with a "translatable label" that you fill in for each language? Seems a bit lame. I'd probably opt for simply making the field itself translatable, and then binding separate tags for each language.

> **Comments:**
> **username_0**: Thanks John. I'll probably go in the direction of creating separate tags for each language.  

---

