Xcode 10 bring a couple of new localization and internationalization features to help iOS and Mac developers reach global audiences.
- Xliff Editor 2 1 – Xcode Localization Made Easy Answers
- Xliff Editor 2 1 – Xcode Localization Made Easy Answer Answers
Here's a wrap-up straight from WWDC 2018's sessions:
Localize Siri intents
The biggest developer news from WWDC was undoubtedly improvements to SiriKit allowing developers to create Siri Shortcuts. 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, as these shortcuts are known in Xcode, are fully localizable. Just select your Intents.intentdefinition file in Xcode, and press the Localize… button in the right-side panel.
IXLIFF allows easy opening and editing of XLIFF files that are currently generated by Xcode. If you are a developer you can use NSLocalizedStrings in your code and the 'Xcode Export Localization' command to easily generate XLIFF files to translate yourself or to send to a translator. If you are a translator, this app is the easiest way to edit the XLIFF files without having to make sure the. Xcode 6 brings XLIFF file format and new localization languages. 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. 1 hour ago Lessons in crisis management and the economic cycle from the story of Joseph, peace be upon him; 2 hours ago Sisi retreat and the victories of the demonstrators. Learn about the gifts of September 20 for Egyptians; 2 hours ago Merkel visited the Russian opposition figure Navalny in the hospital; 2 hours ago. IOS XLIFF files are XCODE generated files, composed of one or more elements. Each element corresponds to an original file or source (e.g. Database table). A contains the source of the localizable data and, once translated, the corresponding localized data for one, and only one, locale.
This document defines version 2.1 of the XML Localisation Interchange File Format (XLIFF). The purpose of this vocabulary is to store localizable data and carry it from one step of the localization process to the other, while allowing interoperability between and among tools.
Xcode will create an Intents.strings 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.
Localize content with Xcode catalogs
This document defines version 2.1 of the XML Localisation Interchange File Format (XLIFF). The purpose of this vocabulary is to store localizable data and carry it from one step of the localization process to the other, while allowing interoperability between and among tools.
Xcode will create an Intents.strings 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.
Localize content with Xcode catalogs
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:
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.
Xcode Internationalization Best Practices
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:
Xliff Editor 2 1 – Xcode Localization Made Easy Answers
- Use Containers — UIStackView and others are already internationalized
- Use Auto Layout — it does the rest of the layout work for you
- Use Formatters — it formats numbers, dates, currencies, and even names for you
- Use color for emphasis — Uppercase and italics don't work in many scripts outside of Latin, but bold text and different colors usually do the same trick
- Check your work — Xcode includes pseudolanguages to test all your assumptions
- Use International Fonts — the built-in app Font Book can tell you which languages your font will work in!
On this last point, Apple reiterates some excellent code to choose appropriate fonts for different alphabets:
Xcode 10 Localization Wrap-up
Xliff Editor 2 1 – Xcode Localization Made Easy Answer Answers
The more things change, the more they stay the same. Xcode localization and internationalization still requires good, honest translators. Ready to localize your app? Contact Benjamin at Babble-on. I'll help you from start to finish!
