Xcode's implementation of Localisation is so odd

Localising my app I found the entire process quite un-swift like (i.e. unsafe and unintuitive) and was not the only one, even the great Paul Hudson also thought it a strange implementation.

Following a tutorial by Andrii Halabuda (https://www.youtube.com/watch?v=_PBA20ZVk1A) relying on an Enum to reduce errors, I found that the strings needed in the "Localizable.strings" strings file could not be avoided.

I have not tried localisation in SwiftUI, I see that it is different, is it easier i.e. can Plists and such be avoided ?

Is there any word on deeper integration that is just more like a normal method ?

Answered by Developer Tools Engineer in 773369022

Hello,

Xcode 15 has made some major improvements to the localization flow this year. Using String Catalogs, you do not need to manually keep .strings files up to date anymore. You can learn more here: https://developer.apple.com/videos/play/wwdc2023/10155/

Accepted Answer

Hello,

Xcode 15 has made some major improvements to the localization flow this year. Using String Catalogs, you do not need to manually keep .strings files up to date anymore. You can learn more here: https://developer.apple.com/videos/play/wwdc2023/10155/

Bem feito.

Xcode's implementation of Localisation is so odd
 
 
Q