/frameworks/base/tools/aapt2/compile/ |
D | PseudolocaleGenerator.cpp | 34 StyleString localized; in pseudolocalizeStyledString() local 37 localized.spans.reserve(string->value->spans.size()); in pseudolocalizeStyledString() 39 localized.spans.push_back(Span{ *span.name, span.firstChar, span.lastChar }); in pseudolocalizeStyledString() 71 iter->updateStart = &localized.spans[i].firstChar; in pseudolocalizeStyledString() 74 Range{ span.firstChar, &localized.spans[i].firstChar, nullptr }); in pseudolocalizeStyledString() 80 iter->updateEnd = &localized.spans[i].lastChar; in pseudolocalizeStyledString() 83 Range{ span.lastChar, nullptr, &localized.spans[i].lastChar }); in pseudolocalizeStyledString() 87 localized.str += localizer.start(); in pseudolocalizeStyledString() 98 *ranges[i].updateStart = localized.str.size(); in pseudolocalizeStyledString() 102 *ranges[i].updateEnd = localized.str.size(); in pseudolocalizeStyledString() [all …]
|
/frameworks/base/docs/html/ndk/downloads/ |
D | downloads_toc.cs | 3 For each document available in translation, add an localized title to this TOC. 4 Do not add localized title for docs not available in translation. 5 Below are template spans for adding localized doc titles. Please ensure that 6 localized titles are added in the language order specified below.
|
/frameworks/base/docs/html/ndk/samples/ |
D | samples_toc.cs | 3 For each document available in translation, add an localized title to this TOC. 4 Do not add localized title for docs not available in translation. 5 Below are template spans for adding localized doc titles. Please ensure that 6 localized titles are added in the language order specified below.
|
/frameworks/base/docs/html/ndk/reference/ |
D | reference_toc.cs | 3 For each document available in translation, add an localized title to this TOC. 4 Do not add localized title for docs not available in translation. 5 Below are template spans for adding localized doc titles. Please ensure that 6 localized titles are added in the language order specified below.
|
/frameworks/base/docs/html/ndk/guides/ |
D | guides_toc.cs | 3 For each document available in translation, add an localized title to this TOC. 4 Do not add localized title for docs not available in translation. 5 Below are template spans for adding localized doc titles. Please ensure that 6 localized titles are added in the language order specified below.
|
/frameworks/base/docs/html/distribute/stories/games/ |
D | rvappstudios-zombie.jd | 29 RV AppStudios launched Zombie Ragdoll localized into 20 languages. 30 In addition to localizing the text within the game, they also localized 57 experience, and by offering a localized game with translation of text and
|
D | g4a-indian-rummy.jd | 2 page.metaDescription=Games4All localized their apps based upon popularity. 35 results — the release of localized versions increased the number of users 67 engagement</b> with the localized versions.
|
D | two-dots.jd | 37 Dots used localized store listing experiments in the Google Play Developer
|
D | dots.jd | 39 Dots used a localized store listing experiment in the Google Play Developer
|
/frameworks/base/docs/html/distribute/tools/ |
D | localization-checklist.jd | 17 <li><a href="#test">5. Test your localized app</a></li> 517 If everything looks good, carefully move the localized directories and files 525 "#test">testing the localized app</a>. 553 5. Test your localized app 576 To test your localized app, you'll need to set up an environment consisting 659 your localized apps. One way to do that is through beta testing with regional 719 localized listing in the Developer Console. 748 Also, since you've made the effort to create a great localized app, let users 756 It's also essential to create localized versions of your promotional graphics 762 can create localized versions of it and then add a link to the correct [all …]
|
D | launch-checklist.jd | 240 The need for localized resources in the app. 246 The need for a localized app description in the Developer Console. 562 updates as well. Later you can add your localized listing details in the 569 creating localized versions of your promotional graphics, screenshots and 574 localized versions of it and then add a link to the correct localized video 622 Play lets you create localized versions of your promotional graphics, 633 you can translate that text and add it to a localized version of the 638 Because your localized graphic assets and videos are so important, you should 764 videos to localized descriptions, release details, and links to your other 772 date, arranging for localized description, high-quality graphic assets, [all …]
|
/frameworks/base/docs/html/google/play/ |
D | developer-api.jd | 50 <li>Editing your app Google Play Store listings, including localized text and 84 <li>Creating and modifying Google Play Store listings, including localized text 99 localized listings in many different locales, you may find this API invaluable. 165 <li>Creating and modifying localized store listings for the app</li>
|
/frameworks/base/docs/html/guide/ |
D | guide_toc.cs | 3 For each document available in translation, add an localized title to this TOC. 4 Do not add localized title for docs not available in translation. 5 Below are template spans for adding localized doc titles. Please ensure that 6 localized titles are added in the language order specified below.
|
/frameworks/base/docs/html/distribute/users/ |
D | your-listing.jd | 120 localized versions of your promotional graphics, screenshots, and videos</a>. 122 localized assets that you’ve provided for that country. Find out more about
|
D | expand-to-new-markets.jd | 75 country. Google Play takes care of providing the appropriate localized 314 Just like your Google Play listing, all other marketing should be localized 317 announcements at local time</strong>. You can build a localized <a href=
|
D | experiments.jd | 82 allowed, to get results faster; particularly for localized tests that may be
|
/frameworks/base/docs/html/work/ |
D | managed-configurations.jd | 127 <strong>Note:</strong> Do not create localized versions of the 169 <em>cannot</em> be localized. It must be specified with a string literal. 174 <code>android:description</code> should be drawn from a localized resource
|
/frameworks/base/docs/html/guide/topics/manifest/ |
D | permission-group-element.jd | 45 as a reference to a string resource, so that it can be localized like other
|
D | permission-tree-element.jd | 44 reference to a string resource, so that it can be localized like other
|
D | intent-filter-element.jd | 78 it can be localized like other strings in the user interface.
|
D | permission-element.jd | 52 reference to a string resource, so that it can be localized like other
|
/frameworks/base/docs/html/preview/features/ |
D | multilingual-support.jd | 45 Spanish strings localized in {@code es_ES} 51 Spanish resources localized under {@code es_ES}. This is because when the system
|
/frameworks/base/docs/html/guide/topics/resources/ |
D | localization.jd | 13 <li>Use resource sets to create a localized app.</li> 15 <li>If localized resources are not available, Android loads your default resources.</li> 55 localized aspects of your application as much as possible from the core Java 127 <code>text_b</code>. This application includes a localized resource file 181 localized</em> string file can contain a subset of the strings, but the
|
D | accessing-resources.jd | 268 all times, so that your application can be localized for other languages. 270 resources (such as localized strings), see <a
|
/frameworks/base/docs/html/training/basics/supporting-devices/ |
D | languages.jd | 104 localized versions of your bitmap drawable. For more information, see <a
|