Answers.Body: <p>Static text on the front-end and Craft CP translations are handled through your <a href="http://buildwithcraft.com/help/static-translations" rel="nofollow">translation files</a>.</p>
  
  <p>All you need to do is name your fields without the translate filter and make sure they have suitable translation arrays in your translation files.</p>
  
  <p>It's also worth mentioning you will need <a href="http://buildwithcraft.com/pricing" rel="nofollow">Craft Pro</a> to take advantage of localisation and translation features.</p>
  
  <p>Here is an example to get you started, this will be added to the translation file for your German locale:</p>
  
  <pre><code>&lt;?php
  
  return array(
      'Surname' =&gt; 'Nachname',
  );
  </code></pre>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-08-11T14:13:27.587Z
Answers.Text: Great! I tryed only to use translations with the filter. Now, without the filter it works as expected!
Answers.UserDisplayName: Tom Bauer
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-08-11T13:24:40.093Z
Answers.LastActivityDate: 2015-08-11T13:24:40.093Z
Answers.UserDisplayName: Jamie Wade
Body: <p>I have content editors that speaks different languages. Is there a way to translate the name and introduction of a field in the control panel? A simple {{ "value"|t }} seams not to work.</p>
  
  <p>Example: English content editors should see "surname" as field name and german speaking editors should see "Nachname".</p>
  
  <p><a href="https://i.sstatic.net/90FR0.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/90FR0.png" alt="Field configuration"></a></p>
  
Tags: <localization><fieldtypes>
Title: Is it possible to translate the name of a field in the CP?
ThreadText: # Is it possible to translate the name of a field in the CP?
  
  (Asked by: username_0 on 2015-08-11)
  
  I have content editors that speaks different languages. Is there a way to translate the name and introduction of a field in the control panel? A simple {{ "value"|t }} seams not to work.
  
  Example: English content editors should see "surname" as field name and german speaking editors should see "Nachname".
  
  [![Field configuration](https://i.sstatic.net/90FR0.png)](https://i.sstatic.net/90FR0.png)
  
  **Tags:** localization, fieldtypes
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2015-08-11. Score: 4 | Accepted answer
  
  Static text on the front-end and Craft CP translations are handled through your [translation files](http://buildwithcraft.com/help/static-translations).
  
  All you need to do is name your fields without the translate filter and make sure they have suitable translation arrays in your translation files.
  
  It's also worth mentioning you will need [Craft Pro](http://buildwithcraft.com/pricing) to take advantage of localisation and translation features.
  
  Here is an example to get you started, this will be added to the translation file for your German locale:
  
  ```
  <?php
  
  return array(
      'Surname' => 'Nachname',
  );
  
  ```
  
  > **Comments:**
  > **username_0**: Great! I tryed only to use translations with the filter. Now, without the filter it works as expected!  
  
  ---
  
  