Hello,
I filed FB23906760 requesting full Persian (fa-IR) system-language support across Apple platforms. A focused Swift/SwiftUI feasibility and QA sample is attached privately to that feedback report.
Apple platforms already provide important building blocks for Persian, including Persian text input, Unicode rendering, locale-aware formatting, semantic right-to-left layout support, and Persian calendar APIs. However, Persian is not currently selectable as a complete system interface language on iOS, iPadOS, or macOS.
The submitted app-level sample exercises:
- runtime RTL/LTR layout switching;
- canonical Persian Kaf (U+06A9) and Yeh (U+06CC);
- ZWNJ (U+200C) preservation;
- LRI/PDI isolation for mixed Persian and Latin content;
- Persian digits and numeric separators;
- Foundation Persian-calendar conversion and month names;
- English/Persian localization-key parity; and
- localized accessibility metadata.
I want to clearly distinguish application localization from operating-system support:
- A Swift or SwiftUI app can provide its own Persian strings through String Catalogs or localized resources.
- SwiftUI and Foundation provide useful primitives for app-level Persian support and repeatable QA.
- An app or sample project cannot add Persian to the system-language selector, translate Apple system UI or first-party apps, or add Persian to Siri, Dictation, Translate, or other system services. Those capabilities require implementation and release by Apple.
The submitted project is therefore reproducible feasibility evidence and a QA seed, not a patch to Apple-owned operating-system resources. Its Persian copy is an AI-assisted engineering draft and is explicitly marked as requiring native linguistic, terminology, accessibility, and in-context review.
I would appreciate guidance from Apple engineers on the following:
- What is the recommended configuration for testing a fully Persian-localized SwiftUI app when Persian is not available as a system UI language?
- Are there documented best practices for testing fa-IR RTL behavior, bidirectional text, VoiceOver metadata, Persian numerals, and Persian-calendar formatting consistently across iOS, iPadOS, and macOS?
- Are there additional developer-specific Feedback Assistant categories that would help Apple evaluate missing Persian support in system services and developer-facing localization infrastructure?
- Would additional fixtures or platform-specific targets be useful as supplements to FB23906760?
More specifically, is there an Apple-recommended way to provide additional technical fixtures, terminology data, or validation cases to the relevant internationalization teams for evaluation of Persian (fa-IR) system-language support?
This is an enhancement request and a technical localization question, not a request for information about unannounced product plans.
Thank you.