From e9d0adb7353d64f303f8df2caec7c742902f26c9 Mon Sep 17 00:00:00 2001 From: Eric Schmidt Date: Sun, 11 Sep 2016 15:51:35 -0700 Subject: docs: Fixed language directory issue. Bug: 31096141 Change-Id: Ibc6789f0381b25ec1449e2b180f20c96cb38a0e3 --- docs/html/preview/features/multilingual-support.jd | 12 ++++++++---- 1 file changed, 8 insertions(+), 4 deletions(-) diff --git a/docs/html/preview/features/multilingual-support.jd b/docs/html/preview/features/multilingual-support.jd index ff21b52d5a8b..e7cd66478f1a 100644 --- a/docs/html/preview/features/multilingual-support.jd +++ b/docs/html/preview/features/multilingual-support.jd @@ -95,10 +95,14 @@ of outcomes like this one.

Android N brings more robust resource resolution, and finds better fallbacks automatically. However, to speed up resolution and improve maintainability, you should store resources in the most common parent dialect. - For example, if you were storing Spanish resources in the {@code es-US} directory - before, move them into the {@code es-419} directory, which contains Latin American Spanish. - Similarly, if you have resource strings in a folder named {@code en-GB}, rename - the folder to {@code en-001} (international English), because the most common + For example, if you were storing Spanish resources + in the {@code values-es-rUS} directory + before, move them into the {@code values-b+es+419} directory, + which contains Latin American Spanish. + Similarly, if you have resource strings in a + directory named {@code values-en-rGB}, rename + the directory to {@code values-b+en+001} (International + English), because the most common parent for en-GB strings is {@code en-001}. The following examples explain why these practices improve performance and reliability of resource resolution.

-- cgit v1.2.3-59-g8ed1b