Answers.Body: <p>No, you're not doing anything wrong. Craft copies the content over to all the other locales when you save an entry for the first time.</p>
  
  <p>The idea behind this is to give content editors a base for the translation, and for some content it’s not even necessary to translate at all. Imagine a text field for city names for example, you don’t need to translate "Berlin" or "New York" for some locales, but for "Berlin and Munich" the German translation would be "Berlin und München".</p>
  
  <p>One feature you might not have discovered is the "Default Entry Status" setting in the section settings. If you disable a locale by default, Craft will still copy over the content on the first save, but the entry won’t be live for this locale yet, you first have to explicitly enable the locale in the right pane of the edit entry view.</p>
  
  <p><a href="https://i.sstatic.net/jd139.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/jd139.png" alt="entry disabled for a locale"></a></p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-04-26T15:07:55.987Z
Answers.Text: Ah brilliant! That worked perfectly. Is it possible though for the 'first save' to _not_ copy content over?
Answers.UserDisplayName: Ben
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-04-26T13:01:45.497Z
Answers.LastActivityDate: 2016-04-26T13:01:45.497Z
Answers.UserDisplayName: carlcs
Body: <p>Currently building a multi-lingual site. Developing locally using WAMP. Using trial version of 'Craft Pro'. Followed the step-by-step instructions of Craft's <a href="https://craftcms.com/docs/localization-guide" rel="nofollow">Setting Up a Localized Site</a> </p>
  
  <p>All works well except for one thing: <strong>Step 3: Define your translatable fields.</strong></p>
  
  <p>I can't make this work. When I check/tick my custom field's “This field is translatable” checkboxes, they don't seem to work as expected. </p>
  
  <h2>Problem</h2>
  
  <p>When I create an entry, put some values in the English locale, then hit save, all values get copied over to the French locale. </p>
  
  <p>This means the moment I hit save, the French version of my site will display English content until I update it with the translation.</p>
  
  <p>Am I doing something wrong?</p>
  
  <p>I'm considering creating locale-specific sections to get around this problem. </p>
  
  <p>Any help, much appreciated.</p>
  
  <p>My current folder structure is as follows:</p>
  
  <ul>
  <li>assets</li>
  <li>craft</li>
  <li>french</li>
  <li>uk</li>
  </ul>
  
Tags: <entries><localization>
Title: I want my custom field values to be stored on a per-locale basis, but can't seem to do this.
ThreadText: # I want my custom field values to be stored on a per-locale basis, but can't seem to do this.
  
  (Asked by: username_0 on 2016-04-26)
  
  Currently building a multi-lingual site. Developing locally using WAMP. Using trial version of 'Craft Pro'. Followed the step-by-step instructions of Craft's [Setting Up a Localized Site](https://craftcms.com/docs/localization-guide)
  
  All works well except for one thing: **Step 3: Define your translatable fields.**
  
  I can't make this work. When I check/tick my custom field's “This field is translatable” checkboxes, they don't seem to work as expected.
  
  ## Problem
  
  When I create an entry, put some values in the English locale, then hit save, all values get copied over to the French locale.
  
  This means the moment I hit save, the French version of my site will display English content until I update it with the translation.
  
  Am I doing something wrong?
  
  I'm considering creating locale-specific sections to get around this problem.
  
  Any help, much appreciated.
  
  My current folder structure is as follows:
  
  * assets
  * craft
  * french
  * uk
  
  **Tags:** entries, localization
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2016-04-26. Score: 1 | Accepted answer
  
  No, you're not doing anything wrong. Craft copies the content over to all the other locales when you save an entry for the first time.
  
  The idea behind this is to give content editors a base for the translation, and for some content it’s not even necessary to translate at all. Imagine a text field for city names for example, you don’t need to translate "Berlin" or "New York" for some locales, but for "Berlin and Munich" the German translation would be "Berlin und München".
  
  One feature you might not have discovered is the "Default Entry Status" setting in the section settings. If you disable a locale by default, Craft will still copy over the content on the first save, but the entry won’t be live for this locale yet, you first have to explicitly enable the locale in the right pane of the edit entry view.
  
  [![entry disabled for a locale](https://i.sstatic.net/jd139.png)](https://i.sstatic.net/jd139.png)
  
  > **Comments:**
  > **username_0**: Ah brilliant! That worked perfectly. Is it possible though for the 'first save' to _not_ copy content over?  
  
  ---
  
  