Introduction

In the previous lesson, you learned how to add string catalogs to your app to help you manage localizable strings. You used Vary by Plural to implement automatic pluralization, but it only works for regular plurals, where you simply add “s” to the noun. When you added a French string catalog, you could provide French translations of English strings, but you couldn’t automate gender and plural agreement of adjectives with the noun argument.

These are all issues of grammatical agreement. Nouns and quantities should agree and, in many languages, quantities, nouns, adjectives and genders should agree. If they don’t, then users reading your app’s text could feel uncomfortable or even irritated. Even worse, if your app refers to all users and associated people as male, those who don’t identify as male might feel excluded to the point where they delete your app from their device.

In this lesson, you’ll:

• Understand the importance of grammatical agreement and inclusive language in enhancing the user experience.

• Analyze the linguistic requirements of an app’s localization strings and use basic inflect blocks and the new Foundation APIs agreeWithArgument and agreeWithConcept to address these requirements.

• Apply the new TermsOfAddress API to implement inclusive language in localized strings within apps.