Lokalisasi iOS: Aliran Kerja Terjemahan Swift dan SwiftUI Natif
iOS menggunakan String Catalogs (Xcode 15+) dan fail .strings/.stringsdict untuk mengurus terjemahan. Paparan SwiftUI dilokalkan secara automatik melalui pemula Text(), dan Xcode mengendalikan pengekstrakan, peraturan pluralisasi, dan eksport ke XLIFF untuk penterjemah. Dengan String Catalogs, anda mendapat editor visual yang menjejak status terjemahan merentas setiap locale yang disokong.
Ciri-Ciri Lokalisasi iOS
Lokalisasi iOS dalam Amalan
Paparan SwiftUI dilokalkan secara automatik apabila anda menggunakan literal rentetan dalam Text(). String Catalogs menguruskan pluralisasi dan variasi peranti dalam satu fail.
// 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 trackingPanduan Berkaitan
Android Localization
Bandingkan lokalisasi iOS dengan corak strings.xml Android dan pengkelayak sumber.
Expo i18n
Terokai lokalisasi Expo untuk membina aplikasi React Native merentas platform dengan fail terjemahan yang dikongsi.
Perbandingan TMS
Bandingkan platform pengurusan terjemahan untuk mencari yang paling sesuai bagi projek iOS anda.
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.
Mulakan Lokalisasi iOS Hari Ini
Urus terjemahan String Catalog iOS anda dengan aliran kerja berkuasa AI, penyegerakan CLI, dan penghantaran CDN di bawah 50ms.