title: iOS Localization: Best Practices
body: <p>What are your best practices regarding Localization for iOS?
  I have been working quite a lot with Localization but it feels like is not good enough and scalable. There needs to be some better way.
  This is my current approach:</p>
  
  <h2>Using .strings files + NSLocalizedString</h2>
  
  <ul>
  <li>This works well. Especially when splitting up the strings file into smaller pieces. But if it's to many small files. It can be tedious to add another language.</li>
  </ul>
  
  <h2>Using .stringsdict for zero, one, many, etc strings</h2>
  
  <ul>
  <li>This also works well. The downside is that is quite a lot "code" for one word.</li>
  </ul>
  
  <h2>Using .strings files for Storyboard</h2>
  
  <ul>
  <li>This is the most tricky part. Generating .string file from a storyboard itself is not hard. But for some reason it's not possible to update strings?? So. if you add more strings into the storyboard file it's not possible to get the new strings into the old strings without regenerating. That means all your old translations will be lost. </li>
  <li>I've read and tested FileMerge. (Works ok, but seems like a long way to go)</li>
  <li>I've read and testat some python scripts. (Don't work at all)</li>
  </ul>
  
  <hr>
  
  <p>I have tried to create a xliff file from Xcode, but never got it to work.
  It always fails to export the file. </p>
  
  <p>Error msg:
  Failed to read strings file ./..../Localizable.strings/ The data couldn’t be read because it isn’t in the correct format.</p>
  
  <p>So.. How do you deal with Localizedstrings in iOS? Especially. What are your approaches around localizating storyboard files? I've seen people setting all the localizedstrings in code. But it feels like a unnecessary step to create a lot of <code>IBOutlets</code> for that cause. </p>