{"id":616,"date":"2014-06-17T11:04:07","date_gmt":"2014-06-17T18:04:07","guid":{"rendered":"http:\/\/www.ibabbleon.com\/copywriter-translator\/?p=616"},"modified":"2018-03-17T10:23:04","modified_gmt":"2018-03-17T17:23:04","slug":"new-xcode-6-localization-ios-yosemite","status":"publish","type":"post","link":"https:\/\/www.ibabbleon.com\/copywriter-translator\/2014\/06\/new-xcode-6-localization-ios-yosemite\/","title":{"rendered":"What’s new in Xcode 6 Localization for iOS 8 and Yosemite"},"content":{"rendered":"

Xcode 6 brings XLIFF file format and new localization languages<\/h1>\n

While developers are poring over the Xcode 6 beta released at WWDC 2014, we’ve been getting questions about some of the big changes and improvements Apple made for localization in iOS 8 and Mac OS X Yosemite. We’ll go in depth in these topics as we update our iOS App Localization Tutorial, but for now here is a recap of the biggest changes.<\/p>\n

Update<\/span> Our new iOS localization tutorial for Xcode 6<\/a> is ready. Check it out!<\/p>\n

XLIFF comes to Xcode with easy import and export<\/h3>\n

Apple touts that the new xliff file<\/strong> file format is an industry standard, which can be used by many localization tools. That’s true. Babble-on has been working with xliff<\/strong> for years, so we’re happy to see this change. (We can still work with your .strings<\/strong> files of course.) Essentially, xliff<\/strong> is just an xml file structured specifically for localization. Rather than having to go through the unintuitive process of using two, separate command-line functions to export your strings for localization, Apple now let’s you do it from the menu bar. Select Editor > Export For Localization<\/span><\/strong><\/p>\n

\"The<\/a>
The localization editor in Xcode 6 makes it much simpler to export your strings.<\/figcaption><\/figure>\n

The exported xliff file<\/strong>\u00a0is actually a combination of ALL your .strings files. Those .strings still exist in Xcode \u2014 you just won’t need to deal with them any more! Once we’ve translated the en.xliff<\/strong> file for you, you’ll get back a new one for each language:\u00a0fr.xliff\u00a0<\/strong>for French,\u00a0es.xliff<\/strong> for Spanish, and so on. Import those into Xcode using the menu\u00a0Editor > Import Localizations<\/strong>. Easy! Having just 1 file per language is a great improvement.<\/span><\/p>\n

In case you do love the command line, Apple also introduced new commands to accomplish the same thing:<\/p>\n

xcodebuild -exportLocalizations -localizationPath <dirpath> -project <projectname> [[-exportLanguage <targetlanguage>]]\r\nxcodebuild -importLocalizations -localizationPath <dirpath> -project <projectname> [-forceImport]<\/span> Import CLI removed from Xcode golden master<\/i>\r\n<\/pre>\n
Preview localizations and pseudolocalizations in Interface Builder<\/h2>\n
Another new feature in Xcode 6 is the ability to view your localizations “live” in Interface Builder. This is a good way of checking that your interface doesn’t break or look sloppy in other languages that are\u00a0more verbose than English (I’m looking at you, German). We hope more developers will take advantage of this tool to improve the design layout for international audiences. In fact, Xcode 6 even lets you preview these issues BEFORE you localize. There is a new Pseudolocalization option for Interface builder offering right-to-left and DOUBLE-length\u00a0options.<\/p>\n
\u00a0Testing your app using Apple’s pseudolanguages<\/span><\/p>\n
    \n
  1. Click the target in the Run<\/strong> destination menu and choose Edit Scheme<\/strong>.<\/li>\n
  2. On the right, select Options<\/strong>.<\/li>\n
  3. Choose a pseudolocalization from the Application Language pop-up menu. Then hit the\u00a0Close<\/strong> button.<\/li>\n
  4. Click Run<\/strong> to relaunch your app in the pseudolanguage.<\/li>\n<\/ol>\n
    Apple’s method is nice because it is built in. However, our developers have told us they like the pseudolocalization files we provide because you can view your texts\u00a0as <\/span>