iOS-lokalisatie: native Swift- en SwiftUI-vertaalworkflows
iOS gebruikt String Catalogs (Xcode 15+) en .strings/.stringsdict-bestanden voor het beheren van vertalingen. SwiftUI-weergaven worden automatisch gelokaliseerd via de Text()-initialiseerder, en Xcode verwerkt extractie, meervoudregels en export naar XLIFF voor vertalers. Met String Catalogs beschikt u over een visuele editor die de vertaalstatus bijhoudt voor elke ondersteunde locale.
iOS-lokalisatiefuncties
iOS-lokalisatie in de praktijk
SwiftUI-weergaven worden automatisch gelokaliseerd wanneer u stringliterals gebruikt in Text(). String Catalogs beheren meervoudsvormen en apparaatvariaties in één bestand.
// 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 trackingGerelateerde Gidsen
Android Localization
Vergelijk iOS-lokalisatie met Android strings.xml en patronen voor resourcekwalificatoren.
Expo i18n
Verken Expo-lokalisatie voor het bouwen van cross-platform React Native-apps met gedeelde vertaalbestanden.
Vergelijkingen van TMS
Vergelijk vertaalbeheerplatforms om het platform te vinden dat het beste bij uw iOS-project past.
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.
Begin vandaag met iOS-lokalisatie
Beheer uw iOS String Catalog-vertalingen met AI-gestuurde workflows, CLI-synchronisatie en CDN-levering onder 50ms.