Question 1

How do I localize a custom UIView with IBLocalizable?

Accepted Answer

Create an extension for your custom view that implements the Localizable protocol by defining the localizableProperty getter and setter, as shown in the README's example for MyCustomView. This maps the property to your view's text elements for seamless integration.

Question 2

IBLocalizable vs NSLocalizedString: which is better?

Accepted Answer

Use IBLocalizable for Interface Builder-heavy workflows to avoid code; it integrates directly into IB. Use NSLocalizedString for more control, programmatic UI, or when managing strings dynamically outside of IB, as IBLocalizable is tied to static IB setups.

Question 3

Does IBLocalizable work with SwiftUI?

Accepted Answer

No, IBLocalizable is designed for UIKit and Interface Builder only. SwiftUI has its own localization system using LocalizedStringKey, so you'll need to use Apple's built-in methods or other SwiftUI-compatible libraries.

Question 4

Can I switch languages dynamically with IBLocalizable?

Accepted Answer

IBLocalizable is primarily set up in Interface Builder and may not handle real-time language switching well without app restart or view reloading. For dynamic changes, you might need additional code to update localized strings manually.

Question 5

How to install IBLocalizable using CocoaPods?

Accepted Answer

Add 'pod 'IBLocalizable'' to your Podfile and run 'pod install'. The README recommends CocoaPods or Carthage for simplicity, with manual installation noted as less ideal.

Question 6

What views does IBLocalizable support out of the box?

Accepted Answer

IBLocalizable supports UILabel, UIButton, UINavigationItem, UIBarItem, UITextField, UITextView, and UISearchBar, as listed in the README. However, support for views like TableView Cells is pending in future updates.

IBLocalizable

What is IBLocalizable?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions