{"id":698,"date":"2018-07-02T12:19:44","date_gmt":"2018-07-02T19:19:44","guid":{"rendered":"http:\/\/www.ibabbleon.com\/copywriter-translator\/?p=698"},"modified":"2018-07-02T12:19:44","modified_gmt":"2018-07-02T19:19:44","slug":"xcode-10-localization-in-ios-12-whats-new-from-apple-from-wwdc-2018","status":"publish","type":"post","link":"https:\/\/www.ibabbleon.com\/copywriter-translator\/2018\/07\/xcode-10-localization-in-ios-12-whats-new-from-apple-from-wwdc-2018\/","title":{"rendered":"Xcode 10 Localization in iOS 12 \u2013 What’s new from Apple from WWDC 2018"},"content":{"rendered":"

Xcode 10 bring a couple of new localization and internationalization features to help iOS and Mac developers reach global audiences.<\/em><\/p>\n

Here’s a wrap-up straight from WWDC 2018’s sessions:<\/p>\n

Localize Siri intents<\/h2>\n

The biggest developer news from WWDC was undoubtedly improvements to SiriKit allowing developers to create Siri Shortcuts<\/strong>. Now, your users can take advantage of personalized voice commands to execute repetitive tasks within your app using Siri. For apps with a global audience, it turns out that Siri intents<\/strong>, as these shortcuts are known in Xcode, are fully localizable. Just select your Intents.intentdefinition<\/code> file in Xcode, and press the Localize…<\/strong> button in the right-side panel.
\n

\"\"<\/a>
Localize Siri Intents files in Xcode 10<\/figcaption><\/figure><\/p>\n

Xcode will create an Intents.strings<\/code> file with all your English texts related to your Siri shortcut. This file will be included automatically in the traditional Xcode export you send your translators.<\/p>\n

Localize content with Xcode catalogs<\/h2>\n

Apple is trying to help developers localize their entire app more efficiently by expanding Xcode’s localization export capabilities. This new localization export is called an Xcode Catalog, and carries the extension .xcloc. Basically, it’s a folder full of stuff rather than just the single xliff from before. The idea is to send the translator everything they need, and for you to receive it back in the same way. The .xcloc includes:<\/p>\n

\"\"<\/a>
Source: Apple.com \u2014 A look inside an xcloc package<\/figcaption><\/figure>\n

Now, instead of exporting only text strings, like the Siri Intent strings we just talked about, Xcode will actually export any content you choose. This includes images that you may want to localize. Before you had to send such non-text content to the translators separately, but now you can have Xcode export and import these assets each time, following your precise directory hierarchy. Another feature of the .xcloc file is including storyboards for context, as well as a general Notes folder. The Notes folder is initially empty, but this is where you can include your own ReadMe file and Screenshots. Apple highly recommends automating your screenshot creation using Tests introduced last year in Xcode 9. It’s a bit of work to set up, but it pays off in the long-run. You’ll be able to send your translators the latest screenshots each time.<\/p>\n\n

The new .xcloc format is supported by the existing Terminal commands for Xcode localization export:<\/p>\n

$ xcodebuild -exportLocalizations -project  -localizationPath  [[-exportLanguage ] ...] <\/targetlanguage><\/dirpath><\/projectname><\/pre>\n
If you’re using Terminal for localization builds currently, you’ll notice this is the same command as before. The only difference is that you are now exporting .xcloc folders instead of just the .xliff files.<\/p>\n
Xcode Internationalization Best Practices<\/h2>\n
Although not much is new in the talk from Apple at WWDC 2018 “Creating Apps for a Global Audience”, it is a great introduction (or review). As always, the key takeaways for “easy” internationalization are:<\/p>\n