Answers.Body: <p>Use the <a href="http://buildwithcraft.com/docs/templating/filters#translate-or-t" rel="noreferrer">translate (or t)</a> filter:</p>
  
  <pre><code>{{label|t}}
  </code></pre>
  
  <p>See <a href="http://buildwithcraft.com/help/static-translations" rel="noreferrer">how to translate static text in templates</a></p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-09-11T01:27:02.317Z
Answers.Text: Brilliant, works perfectly. I didn't think it would work unless it was an actual string like {{ "Something"|t }}.
Answers.UserDisplayName: Patrick Nesbitt
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-09-11T01:15:37.363Z
Answers.LastActivityDate: 2014-09-11T01:15:37.363Z
Answers.UserDisplayName: Marion Newlevant
Answers.Body: <p>Using the <a href="https://github.com/lewisjenkins/craft-lj-dynamicfields/" rel="nofollow">LJ Dynamic Fields</a> plugin, you can also generate drop-down, checkbox, multi-select, and radio button labels/values dynamically from a another channel. If the lookup channel data is localized then the labels will be also. I implemented this for a localized drop-down country list. Works great! and client can control the entries. Powerful plugin.</p>
  
  <pre><code>{% for entry in craft.entries.section('countries').limit(null).order('countryName') %}
    { "value":"{{ entry.countryCode }}" , "label":"{{ entry.countryName }}"}
    {% if not loop.last %},{% endif %}
  {% endfor %}
  </code></pre>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-01-12T22:43:18.037Z
Answers.Text: this is an excellent idea
Answers.UserDisplayName: mjr
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-09-11T08:07:10.980Z
Answers.LastActivityDate: 2014-09-11T08:21:11.190Z
Answers.LastEditDate: 2014-09-11T08:21:11.190Z
Answers.UserDisplayName: Douglas McDonald
Body: <p>Is it possible to have the labels for any of these fields be translatable in templates? I don't mean make the whole field translatable - the same option values would be shared between locales, I would just like the output the label in the correct language.</p>
  
Tags: <localization>
Title: Translating the option labels of Dropdown, Checkboxes or Multi-select fields
ThreadText: # Translating the option labels of Dropdown, Checkboxes or Multi-select fields
  
  (Asked by: username_0 on 2014-09-11)
  
  Is it possible to have the labels for any of these fields be translatable in templates? I don't mean make the whole field translatable - the same option values would be shared between locales, I would just like the output the label in the correct language.
  
  **Tags:** localization
  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_1 on 2014-09-11. Score: 5 | Accepted answer
  
  Use the [translate (or t)](http://buildwithcraft.com/docs/templating/filters#translate-or-t) filter:
  
  ```
  {{label|t}}
  
  ```
  
  See [how to translate static text in templates](http://buildwithcraft.com/help/static-translations)
  
  > **Comments:**
  > **username_0**: Brilliant, works perfectly. I didn't think it would work unless it was an actual string like {{ "Something"|t }}.  
  
  ---
  
  ### Answer by username_2 on 2014-09-11. Score: 2
  
  Using the [LJ Dynamic Fields](https://github.com/lewisjenkins/craft-lj-dynamicfields/) plugin, you can also generate drop-down, checkbox, multi-select, and radio button labels/values dynamically from a another channel. If the lookup channel data is localized then the labels will be also. I implemented this for a localized drop-down country list. Works great! and client can control the entries. Powerful plugin.
  
  ```
  {% for entry in craft.entries.section('countries').limit(null).order('countryName') %}
    { "value":"{{ entry.countryCode }}" , "label":"{{ entry.countryName }}"}
    {% if not loop.last %},{% endif %}
  {% endfor %}
  
  ```
  
  > **Comments:**
  > **username_3**: this is an excellent idea  
  
  ---
  
  