You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The project is using the deprecated .strings files internally. It should be migrated to String Catalogs by right-clicking and choosing migrate. It should really be as simple as that. Xcode should then pick up new localization keys from there using SwiftUI's built-in LocalizedStringKey type.
I could do it myself if I get the "Go" from the core maintainers.
The text was updated successfully, but these errors were encountered:
Alright, I will migrate to String Catalogs then sometime soon. 👍
I could also localize the app using my app TranslateKit for free to support the project. Updating them is easy one click, so I could do it anytime later again. And if machine-translations aren't good enough, we can still remove languages from the supported list while still keeping the translations in the String Catalog for native speakers to review. Saves time in any case.
I will make the app free for open source projects later in the year so anyone can machine-translate new entries long term.
But I'd also happily do it, that could be my way of supporting this awesome project!
Description
The project is using the deprecated .strings files internally. It should be migrated to String Catalogs by right-clicking and choosing migrate. It should really be as simple as that. Xcode should then pick up new localization keys from there using SwiftUI's built-in
LocalizedStringKey
type.I could do it myself if I get the "Go" from the core maintainers.
The text was updated successfully, but these errors were encountered: