TranslateKit 4.1.0 is here! 🇨🇦
New: Canadian English support + Cumulative Selection!
Finally select localization entries across different filters/searches. Perfect for batch operations on 100s of entries. 💪
The best app translation tool continues to get better! 👇
https://translatekit.app
Better late than never: #TranslateKit is now fully compatible with #LiquidGlass! 💦🪟
Sorry for the delay, our app icon is finally out of jail. 💃
Here's a direct comparison – which one do you like better, old or new design?
To add support for Voice Control to this SwiftUI Picker if I use the commented out line everything works as expected.
However, if I use this method, which also returns an array of Strings, those Strings are not put into the Xcode String Catalog for translation.
Is there an easy way around this?
edit: Answer is use an array of LocalizedStringKeys!
#Xcode #StringCatalog #SwiftUI #accessibility #a11y #VoiceControl
Who wants this? 📱🌐
Built it to localize @CrossCraftApp to 7 languages. Drag & drop translation of String Catalogs. Let me know if you’re interested.
#iOSDev #L10n #I18n #StringCatalog
#IndieDev #BuildInPublic #AppLocalization
In some parts of my code Strings weren't getting automatically added to the Xcode 15 String Catalog. Previously what I was doing was manually adding those missing Strings myself.
After reading this blog post from @dvrzan I tried creating those Strings like this in my code. That did the trick and they now get inserted automatically into my String Catalog.
When you add a newline character in code the Xcode 15 String Catalog uses it to format the localization that it shows you. You don't actually "see" the newline character like you do in code.
When you add a translation via the String Catalog that matches it a diff verifies that the newline is present.
Cihat Gündüz
TranslateKit: App Localization
Chris Wu 🪐