All of these changes in localization require you to adopt the latest version of Xcode 13 and Swift. That may be a dealbreaker for some, but if you’ve got Swift code, I highly recommend it. The improvements include: localized Attributed Strings, improved Formatters, and something amazing (?) called Automatic Grammar Agreement.<\/strong><\/p>\n\n\n\n Here’s a breakdown of all the new stuff baked into Xcode 13 localization<\/strong>.<\/p>\n\n\n\n <\/p>\n\n\n\n Formatting text and adding links has always been a pain point in iOS and Mac localization. Many developers give us broken sentences to localize because they want to apply specific formatting (bold<\/strong>, italics<\/em>, etc.), or include a link<\/a>. Localizing plain HTML with formatting and links, by contrast, is straightforward:<\/p>\n\n\n\n In the past, formatted or Attributed Strings<\/strong>, in iOS\/Mac development were complicated. Worse yet, Attributed strings were not<\/span> localizable. (In fact, some developers would mark strings in Xcode as Attributed just so they would not export for translation!)<\/em> In the The developer would then merge the translations together in code, add the formatting often to the wrong word, and insert the link. But grammar and word order are different in other languages<\/strong>, and the translated result was New in Xcode 13 and Swift 5.5, Attributed Strings are:<\/p>\n\n\n\n You can even convert NSAttributedString<\/strong> to the new format for use in UIKit. And Objective-C got a new NSLocalizedAttributedString<\/strong> macro. Together, these changes mean the translator can localize formatted text easily. Now, we can localize that same formatted text like this:<\/p>\n\n\n\n And working with variable values has never been easier. Just pass the values in directly:<\/p>\n\n\n\n Xcode has a new setting Use Compiler to Extract Swift Strings<\/strong> to export these texts, including Attributed strings with string interpolation, automatically. It’s on by default for new projects, but your existing projects will have to opt in:<\/p>\n\n\n\n <\/p>\n\n\n\n <\/p>\n\n\n\n As localizers and translators, we look at dates and numbers differently. International users expect a date or a number to look like it does in their region. iOS and macOS have always allowed users to choose their locale and region, but it is still up to developers to implement these preferences.<\/p>\n\n\n\n Formatters got a lot easier with new Foundation APIs<\/strong>. There are formatters for Date \/ Number \/ ISO8601 \/ Measurement \/ PersonNameComponent<\/strong>, and more.<\/p>\n\n\n\n Now there is no excuse to show a user the wrong date format!<\/p>\n\n\n\n Xcode not only orders the date in the way the user expects, but even includes the translations for the month name automatically. One less thing to pay us to translate, and one less headache for the translator to explain how the punctuation or order is wrong in the app!<\/p>\n\n\n\n Combine this with localized Attributed strings, and you can safely format parts of the date. For example:<\/p>\n\n\n\n Here, all months<\/span> are in a single color, regardless of where they are in the string, or how many characters they take up.<\/p>\n\n\n\n <\/p>\n\n\n\n <\/p>\n\n\n\n As a localization specialist, I want to say “Jiminy, this is amazing!” <\/em><\/strong>Teaching a machine to understand grammar is hard<\/em>. (Am I right, Google Translate?)<\/a> But then you get down to the details, and it is a little less life-changing. But there is <\/em>potential, so let’s take a look at Foundations’s new Automatic Grammar Agreement<\/strong>.<\/p>\n\n\n\n A new option in iOS 15 also allows users to set their \u201dTerm of Address<\/strong>\u201d \u2014 basically, the user’s gender.<\/p>\n\n\n\n This means that you could write Welcome<\/em><\/strong> in Spanish Bienvenido<\/em><\/strong>, and have it automatically appear in the correct gender if the user is a man or a woman:<\/p>\n\n\n\n That’s an improvement, but requires you to use a new custom Markdown format for strings:<\/p>\n\n\n\n BUT\u2026 so far these gender localizations are limited to only Spanish. <\/strong><\/p>\n\n\n\n There are a lot of females speaking other languages, too, so hopefully Apple gets on that for Xcode 14.😛<\/p><\/blockquote><\/figure>\n\n\n\n The main purpose of Automatic Grammar Agreement<\/strong>, however, is to make the translation of plural and gendered texts faster and easier. In English, you might say:<\/p>\n\n\n\n In Spanish, you would need:<\/p>\n\n\n\n English adds an ‘s<\/strong>‘ to the plural form of ‘document<\/strong>‘. But Spanish adds an ‘s<\/strong>‘ to the translations of both ‘open<\/strong>‘ and ‘document<\/strong>‘. Spanish also requires swapping the word order. Other languages will be even more complicated. Some languages have no plural; others have multiple forms of plural. This is why it is best for Xcode, along with translators, to do the pluralization work, not developers.<\/p>\n\n\n\n Automatic Grammar Agreement<\/strong> proposes letting Xcode add those pluralizations \u201cautomatically<\/strong>\u201d. Not only in English, which is pretty easy, but in Spanish, which is harder. Xcode is supposed to understand when the gender of the nouns and adjectives need to change. <\/p>\n\n\n\n For plural items, you would, in theory, need just one line of code, and translations for each word, to translate and have your translators translate separately, but only one form of:<\/p>\n\n\n\n Yet translators would still need to translate the words and<\/em> reorder them so that the noun (documento<\/span>) comes before the adjective (abierto<\/span>). Not much work is saved here, and the complexity has increased.<\/strong><\/p>\n\n\n\n ⛔️ Is this easier than the current method, a stringsdict file<\/a>? Not really. Apple says this is powered by the same technology that offers autocomplete “suggestions” as you type on the keyboard. Right there that tells us grammar agreement can be remarkably intuitive. It can also be an epic fail. ⚠️<\/p>\n\n\n\n But the main reason not to bother with this quite yet is that Automatic Grammar Agreement<\/strong> is limited to only English and Spanish. At least for now. <\/p>\n\n\n\n Hopefully, Apple can expand grammar agreement quickly, or bring Terms of Address<\/strong> to the stringsdict file.<\/p>\n\n\n\n <\/p>\n\n\n\n <\/p>\n\n\n\n Xcode 13 and Swift 5.5 really do make localization easier for developers. The last feature worth mentioning is that Xcode has an xcloc editor built in. Xcloc is the package of translation files, screenshots, and notes you send to your translators<\/a><\/strong> when you Export Localizations\u2026<\/strong> from the Product<\/strong> menu. It isn’t an amazing translation editor, but it can help you add quick comments or screenshots, or review the translations we send you.<\/p>\n\n\n\n So that’s Xcode 13 localization in a blog post! While I would not recommend Automatic Grammar Agreement until it supports more languages and is more fleshed out, I highly recommend adopting the new AttributedString, Formatter APIs, along with the Use Compiler to Extract Swift Strings<\/strong>. All in all, it’s a big year for localization in Xcode, and that’s good news for your international users.<\/p>\n\n\n\n 🇸🇦🇷🇺🇷🇴🇩🇪🇮🇹🇬🇷🇻🇳🇹🇷🇰🇷🇯🇵<\/p>\n","protected":false},"excerpt":{"rendered":" Everything new, shiny, \u201cjust works\u201d, and not-so-great WWDC 2021 brought Xcode 13 and Swift 5.5, the biggest advances to localization we’ve seen for a few years. These are real improvement","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"sfsi_plus_gutenberg_text_before_share":"","sfsi_plus_gutenberg_show_text_before_share":"","sfsi_plus_gutenberg_icon_type":"","sfsi_plus_gutenberg_icon_alignemt":"","sfsi_plus_gutenburg_max_per_row":""},"categories":[37,85,86,5,84],"tags":[94,96,95,80,92,89,65,93],"_links":{"self":[{"href":"https:\/\/www.ibabbleon.com\/copywriter-translator\/wp-json\/wp\/v2\/posts\/732"}],"collection":[{"href":"https:\/\/www.ibabbleon.com\/copywriter-translator\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.ibabbleon.com\/copywriter-translator\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.ibabbleon.com\/copywriter-translator\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.ibabbleon.com\/copywriter-translator\/wp-json\/wp\/v2\/comments?post=732"}],"version-history":[{"count":18,"href":"https:\/\/www.ibabbleon.com\/copywriter-translator\/wp-json\/wp\/v2\/posts\/732\/revisions"}],"predecessor-version":[{"id":782,"href":"https:\/\/www.ibabbleon.com\/copywriter-translator\/wp-json\/wp\/v2\/posts\/732\/revisions\/782"}],"wp:attachment":[{"href":"https:\/\/www.ibabbleon.com\/copywriter-translator\/wp-json\/wp\/v2\/media?parent=732"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.ibabbleon.com\/copywriter-translator\/wp-json\/wp\/v2\/categories?post=732"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.ibabbleon.com\/copywriter-translator\/wp-json\/wp\/v2\/tags?post=732"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}Localized Attributed Strings<\/h2>\n\n\n\n
Please contact us<\/span> <strong><\/span>first<\/span><\/strong><\/span> at<\/span> <a href=\"mailto:localize@ibabbleon.com\"><\/span>Support<\/span><\/a><\/span><\/pre>\n\n\n\nLocalizable.strings<\/code> file, we would get things like:<\/p>\n\n\n\n\"Please contact us \"\n\"first\"\n\" at %@\"<\/span><\/pre>\n\n\n\ngodawful<\/s> imperfect.<\/p>\n\n\n\nAttributedString<\/span>(<\/span>localized:<\/span> \"Please contact us **first** at [Support](mailto:localize@ibabbleon.com)\"<\/span>)<\/pre>\n\n\n\nString<\/span>(localized<\/span>: \"Welcome back, <\/span>\\(username)<\/span>!\"<\/span>) <\/pre>\n\n\n\n![\"\"](\"https:\/\/www.ibabbleon.com\/copywriter-translator\/wp-content\/uploads\/2021\/06\/xcode-use-compiler-to-extract-strings.jpg\")
<\/a>Formatters<\/h2>\n\n\n\n
let<\/span> locale = Locale<\/span>(identifier<\/span>: Locale.current.identifier<\/span>)\nlet<\/span> date = Date<\/span>()\nlet<\/span> now = date.formatted<\/span>(.dateTime.year<\/span>().day<\/span>().month<\/span>().locale<\/span>(locale))\n\/\/ English<\/strong>: Jun 24, 2021\n\/\/ French<\/strong>: 24 juin 2021\n\/\/ Chinese<\/strong> or Japanese<\/strong>: 2021\u5e746\u670824\u65e5<\/span><\/pre>\n\n\n\nvar<\/span> dateString : AttributedString<\/span> {\nvar<\/span> now = date.formatted<\/span>(.dateTime.year().day().month().locale<\/span>(locale).attributed<\/span>)<\/pre>\n\n\n\nlet<\/span> month = AttributeContainer<\/span> \n .dateField(.month<\/span>)\nlet<\/span> color = AttributeContainer<\/span>\n .foregroundColor(.red<\/span>)\nnow.replaceAttributes<\/span>(month, with<\/span>: color)\nreturn<\/span> now\n}\n\/\/ English: <\/span>Jun<\/span> 24, 2021\n\/\/ French: 24 <\/span>juin<\/span> 2021\n\/\/ Chinese or Japanese: 2021\u5e74<\/span>6\u6708<\/span>24\u65e5<\/span><\/pre>\n<\/div><\/div>\n\n\n\nAutomatic Grammar Agreement<\/h2>\n\n\n\n
![\"\"](\"https:\/\/www.ibabbleon.com\/copywriter-translator\/wp-content\/uploads\/2021\/06\/Screen-Shot-2021-06-24-at-1.19.19-PM-1.png\")
<\/a><\/figure>\n<\/div>\n\n\n\n![\"\"](\"https:\/\/www.ibabbleon.com\/copywriter-translator\/wp-content\/uploads\/2021\/06\/Screen-Shot-2021-06-24-at-1.19.34-PM.png\")
<\/a><\/figure>\n<\/div><\/div>\n<\/div>\n<\/div>\n<\/div><\/div>\n\n\n\nBienvenido<\/em> 💁♂️
Bienvenida<\/em><\/strong><\/span><\/code> 🙋🏻♀️<\/p>\n\n\n\n\"^[Welcome](inflect: true)\"<\/span><\/pre>\n\n\n\nYou have 1 open document\nYou have 2 open documents<\/em><\/strong><\/span><\/code><\/pre>\n\n\n\nTienes 1 documento<\/em><\/strong> abierto<\/em><\/strong>
Tienes 2 documentos<\/em><\/strong> abiertos<\/em><\/strong><\/span><\/pre>\n\n\n\nYou have %d open document(s)<\/span><\/em><\/code>. That is:<\/p>\n\n\n\n\"You have ^[\\(count) \\(document) \\(status)](inflect: true)\"<\/span><\/pre>\n\n\n\n\"You have ^[%d %@ %@](inflect: true)\" <\/span>= \"<\/span>Tienes ^[%1$d %3$@ %2$@](inflect: true)\"<\/span>;<\/span>\n\"document\" <\/span>=<\/span> \"documento\"<\/span>;<\/span>\n\"open\"<\/span> =<\/span> \"abierto\"<\/span>;<\/span><\/pre>\n\n\n\n
<\/strong>⛔️ Is it as powerful? No.
<\/strong>⛔️ Does it work in all languages? Not so far.
<\/strong>🤷♀️ Is this future? We’ll have to see.<\/strong><\/p>\n\n\n\nXcode 13 is here<\/h2>\n\n\n\n
![\"\"](\"https:\/\/www.ibabbleon.com\/copywriter-translator\/wp-content\/uploads\/2021\/06\/Screen-Shot-2021-06-25-at-9.31.33-AM-1024x408.png\")
<\/a><\/figure>\n\n\n\n