正文

Software Localization Guide: From String Extraction to Native UX for Android and iOS

/0 浏览量
0909

Localization is not just about swapping English words for Chinese characters. It’s about making a user feel like the app was built specifically for their culture, language, and habits. As someone who has guided dozens of apps from “Hello World” to global marketplaces, I can tell you that the difference between a clunky translation and a seamless native experience often comes down to how you handle the code, the strings, and the culture before you even write a single line of translatable text.

Let’s walk through the entire journey, from pulling strings out of your code to ensuring your Android and iOS apps feel 100% local.

1. Why String Extraction Matters (And Why Most People Get It Wrong)

The first step in localization is string extraction—pulling all user-visible text out of your code and into external files. If you have hardcoded strings like "Welcome, User!" in your Java, Kotlin, Swift, or Objective-C files, you’re already behind.

The Problem with Hardcoded Strings

Imagine this: your app has a button that says "Submit". Later, you decide to expand to German. You change the text to "Absenden". Now, what if you want to add Spanish? French? Japanese? Every time you add a new language, you need to update every file where "Submit" appears. This is error-prone, slow, and unmaintainable.

The Solution: Externalize Strings

Instead, you store all user-visible text in resource files:

  • Android: strings.xml
  • iOS: .strings or .stringsdict files (or Localizable.strings)

This separation allows you to:

  • Update text without touching code
  • Swap translations dynamically
  • Use automated tools to extract and manage strings
  • Collaborate with translators without developer involvement

2. Android Localization: The String Resources System

Android has one of the most robust localization systems out of the box. Let’s dive into how it works and how to set it up correctly.

Step 1: Create String Resources

In your Android project, navigate to res/values/strings.xml. This is where your default (usually English) strings live.

<!-- res/values/strings.xml -->
<resources>
    <string name="app_name">My Awesome App</string>
    <string name="welcome_message">Welcome, %1$s!</string>
    <string name="submit_button">Submit</string>
    <string name="error_message">Something went wrong. Please try again.</string>
    <string name="items_count">%d items selected</string>
</resources>

Notice the placeholders: %1$s for strings, %2$d for integers. These are crucial for handling dynamic content.

Step 2: Add Translations

Create language-specific directories. For Spanish, you’d create res/values-es/strings.xml:

<!-- res/values-es/strings.xml -->
<resources>
    <string name="app_name">Mi App Increíble</string>
    <string name="welcome_message">¡Bienvenido, %1$s!</string>
    <string name="submit_button">Enviar</string>
    <string name="error_message">Algo salió mal. Por favor, inténtalo de nuevo.</string>
    <string name="items_count">%d artículos seleccionados</string>
</resources>

For Japanese:

<!-- res/values-ja/strings.xml -->
<resources>
    <string name="app_name">私の素晴らしいアプリ</string>
    <string name="welcome_message">ようこそ、%1$sさん！</string>
    <string name="submit_button">送信</string>
    <string name="error_message">エラーが発生しました。もう一度お試しください。</string>
    <string name="items_count">%d個のアイテムが選択されました</string>
</resources>

Step 3: Reference Strings in Code

In your Kotlin or Java code, reference these strings using the resource ID:

// Kotlin example
val userName = "Alice"
val welcomeText = getString(R.string.welcome_message, userName)
submitButton.text = getString(R.string.submit_button)

// Java example
String userName = "Alice";
String welcomeText = getString(R.string.welcome_message, userName);
submitButton.setText(getString(R.string.submit_button));

Step 4: Handle Pluralization with Plurals

One of Android’s hidden gems is the <plurals> tag. Languages have different plural rules. English has “1 item” and “2 items,” but Arabic has six plural forms, and Russian has three!

<!-- res/values/strings.xml -->
<resources>
    <plurals name="items_count">
        <item quantity="one">%d item selected</item>
        <item quantity="other">%d items selected</item>
    </plurals>
</resources>

<!-- res/values-ar/strings.xml (Arabic has 6 plural forms) -->
<resources>
    <plurals name="items_count">
        <item quantity="zero">لا توجد عناصر</item>
        <item quantity="one">عنصر واحد</item>
        <item quantity="two">عنصران</item>
        <item quantity="few">%d عناصر</item>
        <item quantity="many">%d عنصراً</item>
        <item quantity="other">%d عنصر</item>
    </plurals>
</resources>

To use plurals in code:

val count = 5
val text = resources.getQuantityString(R.plurals.items_count, count, count)
textView.text = text

This ensures the correct plural form is used for every language, which is critical for a native feel.

Step 5: RTL (Right-to-Left) Support

For languages like Arabic and Hebrew, you need to support RTL layouts. Android makes this relatively easy:

  1. Add layoutDirection support in your manifest:
<application
    android:supportsRtl="true"
    ...>

  1. Use material design components or update your layouts to use marginStart/marginEnd instead of marginLeft/marginRight.

  2. Test thoroughly. RTL can break layouts if you use absolute positioning.

3. iOS Localization: The Assets and Strings System

iOS localization is equally powerful but has some nuances. Let’s explore how to set it up.

Step 1: Create Localizable.strings

In Xcode, create a new file: File > New > File > Strings File. Name it Localizable.strings.

// Localizable.strings (English)
"app_name" = "My Awesome App";
"welcome_message" = "Welcome, %@";
"submit_button" = "Submit";
"error_message" = "Something went wrong. Please try again.";
"items_count" = "%lu items selected";

Step 2: Add Language Versions

In Xcode, select your project target, go to the “Info” tab, and under “Localizations,” add the languages you want to support (e.g., Spanish, Japanese, Arabic).

Xcode will automatically create language-specific .strings files:

  • Localizable.strings (Spanish)
  • Localizable.strings (Japanese)

Step 3: Reference Strings in Code

In Swift:

let userName = "Alice"
let welcomeText = String(format: NSLocalizedString("welcome_message", comment: ""), userName)
submitButton.setTitle(NSLocalizedString("submit_button", comment: ""), for: .normal)

In Objective-C:

NSString *userName = @"Alice";
NSString *welcomeText = [NSString stringWithFormat:NSLocalizedString(@"welcome_message", nil), userName];
[submitButton setTitle:NSLocalizedString(@"submit_button", nil) forState:UIControlStateNormal];

Step 4: Handle Pluralization with .stringsdict

iOS uses .stringsdict files for pluralization, which is more powerful than Android’s approach.

Create a Localizable.stringsdict file:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
    <key>items_count</key>
    <dict>
        <key>NSStringLocalizedFormatKey</key>
        <string>%#@items@</string>
        <key>items</key>
        <dict>
            <key>NSStringFormatSpecTypeKey</key>
            <string>NSStringPluralRuleType</string>
            <key>NSStringFormatValueTypeKey</key>
            <string>lu</string>
            <key>one</key>
            <string>%#@items@</string>
            <key>other</key>
            <string>%lu items selected</string>
        </dict>
    </dict>
</dict>
</plist>

For Arabic, you’d add more plural forms:

<key>zero</key>
<string>لا توجد عناصر</string>
<key>one</key>
<string>عنصر واحد</string>
<key>two</key>
<string>عنصران</string>
<key>few</key>
<string>%lu عناصر</string>
<key>many</key>
<string>%lu عنصراً</string>
<key>other</key>
<string>%lu عنصر</string>

To use in code:

let count: UInt = 5
let format = NSLocalizedString("items_count", comment: "")
let text = String(format: format, locale: Locale.current, count)

Step 5: RTL Support in iOS

iOS handles RTL automatically if you use Auto Layout properly:

  1. Use leading and trailing constraints instead of left and right
  2. Test in a RTL language (Arabic or Hebrew) to ensure layouts flip correctly
  3. Use UIView.semanticContentAttribute = .forceRightToLeft if needed

4. Common Pitfalls and How to Avoid Them

Pitfall 1: Text Expansion

German text is often 30-40% longer than English. Japanese text can be more compact vertically but wider horizontally. If your UI has fixed-width buttons or labels, text will overflow.

Solution: Use flexible layouts, allow text wrapping, and test with the longest translations.

Pitfall 2: Gendered Languages

Languages like French, Spanish, and Arabic have gendered adjectives and nouns. “Welcome” in French is “Bienvenue” (neutral), but “You are welcome” changes based on the gender of the person you’re addressing.

Solution: Use placeholders and dynamic strings. Avoid hardcoding gendered forms.

Pitfall 3: Date and Time Formats

Different cultures use different date formats:

  • US: MM/DD/YYYY
  • EU: DD/MM/YYYY
  • Japan: YYYY/MM/DD

Solution: Use DateFormatter (iOS) and DateTimeFormatter (Android) with locale-specific patterns.

// iOS
let formatter = DateFormatter()
formatter.dateFormat = "MMM dd, yyyy"
formatter.locale = Locale.current
let dateString = formatter.string(from: Date())

// Android
val formatter = SimpleDateFormat("MMM dd, yyyy", Locale.getDefault())
val dateString = formatter.format(Date())

Pitfall 4: Numbers and Currencies

Numbers and currencies vary wildly:

  • Some cultures use commas as decimal separators (e.g., 1.234,56 in German)
  • Currency symbols change (€, $, ¥, ₹)

Solution: Use NumberFormatter and CurrencyFormatter with locale settings.

// iOS
let currencyFormatter = NumberFormatter()
currencyFormatter.numberStyle = .currency
currencyFormatter.locale = Locale.current
let priceString = currencyFormatter.string(from: 1234.56)

// Android
val currencyFormatter = NumberFormat.getCurrencyInstance(Locale.getDefault())
val priceString = currencyFormatter.format(1234.56)

Pitfall 5: Missing Translations

What happens when a user switches to a language you haven’t translated yet?

Solution: Always provide a fallback. On Android, the default strings.xml is automatically used. On iOS, you can set a fallback language in your app’s settings.

5. Advanced: Contextual Localization

Sometimes, the same English word needs different translations based on context. For example, “File” could mean:

  • A document (noun) → “文件” in Chinese
  • To file a report (verb) → “提交” in Chinese

Solution: Use distinct string keys for different contexts:

<!-- Android -->
<string name="file_document">File</string>
<string name="file_action">File Report</string>

// iOS
let fileDocument = NSLocalizedString("file_document", comment: "Noun: a document")
let fileAction = NSLocalizedString("file_action", comment: "Verb: to submit a report")

6. Testing Your Localization

Automated String Extraction

Use tools to ensure all strings are extracted:

  • Android: android-lint with the MissingTranslation check
  • iOS: Xcode’s built-in localization validation

Manual Testing

  1. Switch your device language to each target language
  2. Check for:
    • Text overflow
    • Cut-off words
    • Incorrect pluralization
    • RTL layout issues
    • Date/time/number formatting

Professional Translation Tools

Consider using platforms like:

  • Crowdin
  • Transifex
  • POEditor
  • Phrase

These tools integrate with your version control system and allow collaborative translation management.

7. Cultural Considerations Beyond Translation

Localization isn’t just about language. It’s about culture.

Images and Icons

  • Some gestures are offensive in certain cultures (e.g., the “thumbs up” sign)
  • Colors have different meanings (white is mourning in some Asian cultures)
  • Models and clothing should reflect local diversity

Content and Features

  • Payment methods vary (Alipay in China, iDEAL in Netherlands)
  • Social features may need adjustment (WeChat integration in China)
  • Legal requirements differ (GDPR in Europe, COPPA in the US)

Keyboard and Input

  • Support right-to-left keyboards
  • Enable predictive text in the target language
  • Test with local input methods (e.g., Chinese pinyin, Japanese kana)

8. Code Examples: Full Implementation

Android: Complete Localization Setup

strings.xml

<?xml version="1.0" encoding="utf-8"?>
<resources>
    <string name="app_name">TaskMaster</string>
    <string name="welcome_message">Hello, %1$s!</string>
    <string name="submit_button">Submit</string>
    <string name="error_message">An error occurred. Please try again.</string>
    <string name="items_count">%d tasks completed</string>
    
    <plurals name="tasks_count">
        <item quantity="one">%d task completed</item>
        <item quantity="other">%d tasks completed</item>
    </plurals>
    
    <string name="date_format">MMMM dd, yyyy</string>
    <string name="currency_format">$#,##0.00</string>
</resources>

MainActivity.kt

class MainActivity : AppCompatActivity() {
    override fun onCreate(savedInstanceState: Bundle?) {
        super.onCreate(savedInstanceState)
        setContentView(R.layout.activity_main)
        
        val userName = "Alice"
        val welcomeText = getString(R.string.welcome_message, userName)
        welcomeTextView.text = welcomeText
        
        val taskCount = 5
        val tasksText = resources.getQuantityString(R.plurals.tasks_count, taskCount, taskCount)
        tasksTextView.text = tasksText
        
        val dateFormat = SimpleDateFormat(getString(R.string.date_format), Locale.getDefault())
        val dateString = dateFormat.format(Date())
        dateTextView.text = dateString
        
        val currencyFormat = NumberFormat.getCurrencyInstance(Locale.getDefault())
        val priceString = currencyFormat.format(1234.56)
        priceTextView.text = priceString
    }
}

strings-es.xml

<?xml version="1.0" encoding="utf-8"?>
<resources>
    <string name="app_name">TaskMaster</string>
    <string name="welcome_message">¡Hola, %1$s!</string>
    <string name="submit_button">Enviar</string>
    <string name="error_message">Ocurrió un error. Por favor, inténtalo de nuevo.</string>
    <string name="items_count">%d tareas completadas</string>
    
    <plurals name="tasks_count">
        <item quantity="one">%d tarea completada</item>
        <item quantity="other">%d tareas completadas</item>
    </plurals>
    
    <string name="date_format">dd MMMM yyyy</string>
    <string name="currency_format">€#,##0.00</string>
</resources>

iOS: Complete Localization Setup

Localizable.strings

"app_name" = "TaskMaster";
"welcome_message" = "Hello, %@";
"submit_button" = "Submit";
"error_message" = "An error occurred. Please try again.";
"items_count" = "%lu tasks completed";

Localizable.stringsdict “`xml <?xml version=“1.0” encoding=“UTF-8”?> <!DOCTYPE plist PUBLIC “-//Apple//DTD PLIST 1.0//EN” “http://www.apple.com/DTDs/PropertyList-1.0.dtd”> 

<key>items_count</key>
<dict>
    <key>NSStringLocalizedFormatKey</key>
    <string>%#@tasks@</string>
    <key>tasks</key>
    <dict>
        <key>NSStringFormatSpecTypeKey</key>
        <string>NSStringPluralRuleType</string>
        <
-- 展开阅读全文 --