localization

# Localization

Modern iOS localization using String Catalogs (.xcstrings) for managing translations, plural forms, and locale-aware content. Supports SwiftUI's LocalizedStringKey and String(localized:) APIs.

## Reference Loading Guide

**ALWAYS load reference files if there is even a small chance the content may be required.** It's better to have the context than to miss a pattern or make a mistake.

| Reference | Load When |
|-----------|-----------|
| **[String Catalogs](references/string-catalogs.md)** | Setting up or using Xcode 15+ String Catalogs |
| **[Pluralization](references/pluralization.md)** | Handling plural forms, stringsdict migration |
| **[Formatting](references/formatting.md)** | Date, number, currency locale-aware formatting |
| **[RTL Support](references/rtl-support.md)** | Right-to-left layouts, semantic directions |

## Core Workflow

1. Create String Catalog in Xcode (File > New > String Catalog)
2. Mark strings with `String(localized:comment:)` or use SwiftUI's automatic extraction
3. Add plural variants in String Catalog editor where needed
4. Test with pseudo-localization (Scheme > Run > Options > App Language)
5. Export for translation (File > Export Localizations)

## Key Patterns

```swift
// SwiftUI - automatic localization
Text("Welcome")
Button("Continue") { }

// Explicit localization with context
let title = String(localized: "Settings", comment: "Navigation title")

// Deferred localization for custom views
struct CardView: View {
    let title: LocalizedStringResource
    var body: some View { Text(title) }
}
```

## Build Settings

- **Use Compiler to Extract Swift Strings**: Yes
- **Localization Prefers String Catalogs**: Yes

## Common Mistakes

1. **Forgetting String Catalog in Build Phases** — Adding String Catalog but forgetting to check "Localize" in File Inspector means it's not embedded. Always verify in Build Phases > Copy Bundle Resources.

2. **Pseudo-localization not tested** — Not running your app with pseudo-loca