It's been many years since I last wrote about Android pseudolocalization [https://blog.danlew.net/2015/04/06/pseudolocalization-visiting-androids-bizarro-world/]. There's even some official documentation [https://developer.android.com/guide/topics/resources/pseudolocales] now! I'm back because of two small speedbumps I've since run into when using pseudolocalization. Why Isn't It

Localization is an important topic to me; there's no faster way to expand your audience than include the entire rest of the world! A few months ago I wrote about how to setup your strings [https://blog.danlew.net/2014/04/16/android-localization-tips/]. That's only half the battle - it

I've been interested in localization on Android recently. There's a few neat things I've been experimenting with I thought I'd share. xliff:g One common problem when sending strings for translation is that some parts of a string should not be localized. For example, suppose I've got this string: Hello,