Vai al contenuto
iOS i18n

Localizzazione iOS: Flussi di Lavoro Nativi per la Traduzione in Swift e SwiftUI

iOS utilizza i String Catalog (Xcode 15+) e i file .strings/.stringsdict per gestire le traduzioni. Le view SwiftUI vengono localizzate automaticamente tramite l'inizializzatore Text(), e Xcode gestisce l'estrazione, le regole di pluralizzazione e l'esportazione in XLIFF per i traduttori. Con i String Catalog si ottiene un editor visivo che traccia lo stato della traduzione per ogni locale supportato.

Funzionalità di Localizzazione iOS

Cataloghi di stringhe (.xcstrings) con editor visivo per le traduzioni e monitoraggio dello stato
Localizzazione automatica SwiftUI tramite Text() e LocalizedStringKey
Pluralizzazione e concordanza grammaticale tramite .stringsdict e motore grammaticale automatico
Esportazione/importazione XCLOC per la consegna professionale ai traduttori tramite Xcode
Localizzazione di Storyboard e XIB con integrazione Interface Builder
Vincoli Auto Layout che si adattano alla lunghezza del testo e alle variazioni della direzione del layout
Supporto right-to-left (RTL) con semantica di layout leading/trailing
Formattatori Foundation per date, numeri e misure in base al locale
Localizzazione del bundle dell'app con directory .lproj per risorse specifiche per locale

Localizzazione iOS in pratica

Le viste SwiftUI vengono localizzate automaticamente quando si utilizzano stringhe letterali in Text(). I cataloghi di stringhe gestiscono la pluralizzazione e le variazioni per dispositivo in un unico file.

// SwiftUI - Automatic localization
struct WelcomeView: View {
    let name: String

    var body: some View {
        VStack {
            // Automatically looks up "Welcome to %@" in String Catalog
            Text("Welcome to \(name)")

            // Pluralization via String Catalog
            Text("^[\(itemCount) item](inflect: true)")

            // Date formatting respects locale
            Text(Date.now, format: .dateTime.month(.wide).day())
        }
    }
}

// Localizable.xcstrings (String Catalog)
// Managed in Xcode - supports:
// - Automatic extraction from SwiftUI
// - Pluralization rules per locale
// - String variation by device
// - Translation state tracking

iOS Localization — Frequently Asked Questions

What is the recommended approach for iOS localization in 2026?

Apple's recommended approach is String Catalogs (.xcstrings), introduced in Xcode 15. String Catalogs replace the older .strings and .stringsdict files with a single JSON-based file that supports all plural rules, device-specific variants, and string variations. Xcode automatically extracts localizable strings from your Swift and SwiftUI code, and tracks translation completion percentage per locale.

How does Better I18N work with Xcode and String Catalogs?

Better I18N uses its CLI to export translations from your String Catalogs, push them to the dashboard for professional translation or AI-assisted translation, then import the translated files back into Xcode. The workflow is: `better-i18n push` exports your .xcstrings file, translators work in the Better I18N dashboard, and `better-i18n pull` downloads the completed translations back into Xcode format. This replaces manual .xcloc file management.

What is the difference between NSLocalizedString and SwiftUI's native localization?

NSLocalizedString is the UIKit/AppKit API that looks up a key in your .strings bundle. SwiftUI's Text() view performs automatic localization — it uses the string literal as the key itself, which means your source code is self-documenting. Both approaches work with String Catalogs in Xcode 15+. For new SwiftUI projects, the automatic approach is cleaner; for UIKit projects maintaining existing .strings files, NSLocalizedString remains the standard.

How do I implement RTL (right-to-left) support on iOS?

iOS handles RTL layout automatically when the user selects an RTL language like Arabic or Hebrew. SwiftUI's layout system uses leading/trailing instead of left/right, and UIKit respects UIView.semanticContentAttribute. The key is to avoid hardcoded left/right margins and use Auto Layout with leading/trailing constraints. Better I18N supports Arabic and Hebrew as target languages and handles bidirectional text in the translation editor.

Can I use over-the-air (OTA) translation updates on iOS?

Apple's App Store review policy requires that core app functionality not change between reviews, but translation content updates are generally permitted via OTA mechanisms. Better I18N's native Swift SDK (BetterI18n) fetches translations from the CDN at runtime, allowing you to push translation corrections and new language support without an app store release. The SDK uses a two-phase load: it reads from local storage first for instant display, then refreshes from CDN in the background.

What pluralization rules does iOS support and how many are there?

iOS supports all Unicode CLDR plural categories: zero, one, two, few, many, and other. Not all languages use all categories — English only uses one and other, while Arabic uses all six. String Catalogs in Xcode 15 automatically show the relevant plural forms for each target locale. Better I18N's translation editor also surfaces the correct plural forms per language so translators never miss a required plural case.

Inizia la localizzazione iOS oggi

Gestisci le traduzioni del tuo catalogo di stringhe iOS con flussi di lavoro basati sull'AI, sincronizzazione tramite CLI e distribuzione CDN in meno di 50 ms.