Android Best Practices – String resources cheat sheet

Android runs on many devices in many regions. Any application should handle text and numbers in ways appropriate to the locales where the app is used. Using a Localization management platform to manage the String resources brings many benefits:

- Automate. New strings can be put to your codebase automatically (#FailFast)
- Collaborate. Allows many people to work on your translation project (translators, product team, etc.)
- Statistics. So you don’t miss what is important

See http://renaudmathieu.fr/android-best-practices-string-resources-cheat-sheet/ for further details.

Transcript

1. Viadeo September 2016 Mobile Transla/on cheat sheet Languages are complex, so namespaces are necessary to bring context and break ambiguity. Name your strings with keys that resemble namespaces. Think Features. (onboarding_xx, joboffer_yy, etc.) Don’t be afraid of repea;ng a value for two or more keys. Don’t write string values in all uppercase. No HTML tags Use plurals and don’t forget that 0 is plural in English #1 #2 #3 #4 #5 #6 #7 Plurals are specials, use plurals_xx_yy format joboffer.descrip/on joboffer.descrip;on joboffer.descrip/on.see_more joboffer.descrip;on.see_more login.login_buFon splash.login_buFon login Se connecter SE CONNECTER Un texte Un <b>texte</b> plurals_joboffer_count joboffer_count