Android will select the right locale based on the device language if it is available in your published application. With an elaborate copywriting process you might want to separate the developer locale used for development (maybe containing placeholder copy) and the English, edited and proof-read language version.Īnd voila: you’re done! There is no extra code for language selection needed. If a string is not translated in a locale, the app will automatically fall back to the value in the default strings.xml - usually the English language file will be used as a default language. You can now start translating your strings. You may need to close and re-open the Translation Editor tab after adding a new language if it does not show up immediately. In the Translation Editor, click the globe-icon to add a new language file, in our example we will add ‘de’ (German) and ‘es"(Spanish). In your projects file navigator, expand the newly created values directory, right-click the strings.xml file to open the Translation Editor.
Translating With The Android Studio Translation Editor Go ahead, follow the tooltip and move all your translatable strings to the strings.xml resource file. If you hover your cursor over a UI widget, Android Studio shows a tooltip that offers to move this hard-coded string to a resource file named strings.xml. We used this little example view (to the right) that we will be using for this post.īy default, UI widgets store their label in hard-coded strings. If this is your first Android Studio project: simply install Android Studio, create a new project from the “Blank Activity” template and drag some UI widgets to the blank canvas space.
Shall we start? Getting StartedĪndroid Studio is the official Android IDE being developed by Google. This tutorial will guide you through the process of creating a multilingual Android app with Android Studio.
Localizing your Android app can boost sales, increase conversion rates, and improve the overall user experience for your app.
0 kommentar(er)
