It’s surprisingly easy to configure your project with multiple strings then have it choose one at runtime based on available space.
First, press Cmd+N in Xcode to make a new file, then choose “Stringsdict file” – this is a property list XML file containing string settings. Name it “Localizable.stringsdict”, so that iOS picks it up automatically.
Right-click on the new Localizable.stringsdict file in your Xcode project, then choose Open As > Source Code so you can see the XML inside. You should see that it ends like this:
Add this new XML directly before those two lines:
<key>Login</key> <dict> <key>NSStringVariableWidthRuleType</key> <dict> <key>100</key> <string>Login.</string> <key>200</key> <string>You must login before continuing.</string> <key>300</key> <string>Please enter your username and password to continue.</string> </dict> </dict>
That defines a single string key, “Login”, but provides three size variations: one for very little space (size 100), one for a medium amount of space (size 200), and one for lots of space (size 300). These size integers mean nothing to iOS – you can use any numbers that make sense to you, but increments of 100 leave you lots of space to insert new values in between later on.
Now that you have a width-varying string to work with, you can pass that to
NSLocalizedString(). Note that you must cast the result to an
let localized = NSLocalizedString("Login", comment: "Prompt for user to log in.") as NSString
variantFittingPresentationWidth() with a size integer of your choosing:
label.text = localized.variantFittingPresentationWidth(300)
That method only exists on
NSString, hence the earlier typecast.
You can pass any integer you want into
variantFittingPresentationWidth() – iOS will automatically resolve it to find the best match in your strings dictionary, counting downwards where necessary. For example, if you tried loading a string with width 500, the 300 string would be returned, but if you tried 299 then the 200 string would be returned.
Sponsored You’re already busy updating your app for Swift 4.2 and iOS 12, so why not let Instabug help you find and fix bugs? Add just two lines of code to your project and receive comprehensive reports with all the feedback you need to ship a world-class app – click here to learn more!
Available from iOS 9.0
Did this solution work for you? Please pass it on!
Other people are reading…
About the Swift Knowledge Base
This is part of the Swift Knowledge Base, a free, searchable collection of solutions for common iOS questions.