Prior to Android N, Android could not always successfully - match app and system locales. For example, suppose that your app's default language - is US English, but that it also has Spanish strings localized in {@code es_ES} - resource files.
-When your Java code referred to strings, it would resolve string languages as -follows:
-For example, assume that you have the following situation:
+When your Java code refers to strings, the system would load +strings from the default ({@code en_US}) resource file, even if the app has +Spanish resources localized under {@code es_ES}. This is because when the system + cannot find an exact match, it continues to look for resources by stripping the + country code off the locale. Finally, if no match is found, the system falls + back to the default, which is {@code en_US}.
-These resolution problems arose because the system stripped the country code - off of the locale if it could not find an exact match. For example:
+The system would also default to {@code en_US} if the user chose a language that +the app didn't support at all, like French. For example:
+Table 1. Resource resolution without an exact locale match.