Generate iOS localization as String Catalogs - #995
Merged
Conversation
The localization generator writes one .xcstrings catalog per table (app, InfoPlist, widget) instead of per-language .lproj/.strings files, and generates the typed Localized.swift and WidgetLocalized.swift accessors itself. SwiftGen is removed from the toolchain.
DRadmir
force-pushed
the
wt4/xcstrings-localization
branch
from
August 31, 2026 23:30
4035d4a to
49ebc98
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Replaces the per-language iOS
.stringsfiles with.xcstringsString Catalogs, one per table, so a translation change touches a single file instead of 31. The typedLocalizedaccessors are now produced by the localization generator and SwiftGen is no longer needed.