文法上の性別でアプリの UI をパーソナライズする

30 億人もの人々が、性別で文法が変わる言語を話します。こうした言語では、話す相手、または言及する人や物の性別に応じて、各文法範疇（名詞、動詞、形容詞、前置詞など）の語形が変化します。伝統的に、性別で文法が変わる多くの言語では、男性形をデフォルトまたは汎用の性別として使用しています。

女性を男性形で呼ぶなど、ユーザーに対して不適切な文法性別を表記すると、ユーザーのパフォーマンスや態度に悪影響を及ぼす可能性があります。一方、ユーザーの文法的性を適切に反映した言語を使用して UI を作成すると、ユーザー エンゲージメントが向上し、より自然でパーソナライズされたユーザー エクスペリエンスを提供できます。

To help you build a user-centric UI for gendered languages, Android 14 introduces the Grammatical Inflection API, which lets you add support for grammatical gender without refactoring your app.

Example of inflection for grammatical gender

In gendered languages, grammatical gender can't be worked around the same way as it can in English. For example, in English to write a message telling the user that they are subscribed to your app's service, you could use a single phrase: "You are subscribed to...".

To provide a similar phrase in French, there are a few options:

• Masculine-inflected form: "Vous êtes abonné à..." (English: "You are subscribed to...")
• Feminine-inflected form: "Vous êtes abonnée à..." (English: "You are subscribed to...")
• Neutral phrasing that avoids inflection: "Abonnement à...activé" (English: "Subscription to ... enabled")

Similar to English, the first two options address the user directly. However, without any mechanism to accommodate this grammatical feature of French, you would only have the third option, which changes the tone of the message and might not be what you want to display in your user interface.

In these cases, the Grammatical Inflection API lowers the effort to display strings relative to the viewer's grammatical gender—that is, the person who's viewing the UI, not who's being talked about. To show users personalized translations in your app, add translations that are inflected for each grammatical gender for affected languages and then use the GrammaticalInflectionManager API to adjust which translations are shown to each user.

In many languages, grammatical gender also applies to regular nouns in addition to people. For example, in French the word chaise (chair) is feminine, whereas oiseau (bird) is masculine. For situations other than addressing the user, you can use the existing ICU SelectFormat API.

Implement the API

After the user has indicated their grammatical gender (for example, either through a settings section of your app or a user setup workflow), you can use the setRequestedApplicationGrammaticalGender(int) method to store the value in your app's resources configuration.

For example, if you want to set a user's preferred grammatical gender to feminine, you would ask the user to select which grammatical gender they prefer and then call the API:

// Set app's grammatical gender to feminine
val gIM = mContext.getSystemService(GrammaticalInflectionManager::class.java)
gIM.setRequestedApplicationGrammaticalGender(
    Configuration.GRAMMATICAL_GENDER_FEMININE)

// Set app's grammatical gender to feminine
GrammaticalInflectionManager gIM =
    mContext.getSystemService(GrammaticalInflectionManager.class);
gIM.setRequestedApplicationGrammaticalGender(
    Configuration.GRAMMATICAL_GENDER_FEMININE);

Here is example of how to declare configuration changes in your app's manifest file if you want to handle them yourself:

<activity android:name=".TestActivity"
              android:configChanges="grammaticalGender"
              android:exported="true">
</activity>

If your app needs to check the grammatical gender in the current resource configuration, you can use the getApplicationGrammaticalGender() method to retrieve it:

val gIM = mContext.getSystemService(GrammaticalInflectionManager::class.java)
val grammaticalGender = gIM.getApplicationGrammaticalGender()

GrammaticalInflectionManager gIM =
    mContext.getSystemService(GrammaticalInflectionManager.class);
int grammaticalGender = gIM.getApplicationGrammaticalGender();

Add translations for languages with grammatical gender

To provide localized text for languages with grammatical gender, create an alternative resources file and append the grammatical gender qualifier immediately after the locale name for those languages. The following table outlines the possible values:

You should only include strings that support grammatical gender inflections in these resources files. All strings must have a value in the default resource file that contains other localized strings. This default translation is shown whenever a gender-inflected translation is not available.

In the example provided for French earlier, the neutral phrasing would be the value of the string in the default resources res/values-fr/strings.xml file. The following code snippets show how each resource file would be formatted to accommodate all the grammatical variations from the example in French:

<resources>
    ...
    <string name="example_string">Vous êtes abonnée à...</string>
</resources>

<resources>
    ...
    <string name="example_string">Vous êtes abonné à...</string>
</resources>

<resources>
    ...
    <string name="example_string">Abonnement à...activé</string>
</resources>