Question 1

How do I integrate nslocalizer into my Xcode build phase?

Accepted Answer

Add a run script phase to your Xcode target and invoke nslocalizer with --project and --target flags, as shown in the README's integration example, to automate checks during builds.

Question 2

nslocalizer vs Xcode's built-in localization tools: which is better?

Accepted Answer

nslocalizer excels at automated, granular audits for missing and unused strings, while Xcode's tools are more integrated for general localization but may require manual effort for detailed string analysis.

Question 3

Does nslocalizer work with SwiftUI or only UIKit/AppKit?

Accepted Answer

It analyzes NSLocalizedStrings, so if SwiftUI code uses NSLocalizedString directly or via bridging, it can work, but SwiftUI's native LocalizedStringKey might not be detected without additional setup.

Question 4

Can nslocalizer handle strings in storyboards or XIB files?

Accepted Answer

The README focuses on code analysis, so it might miss strings embedded in Interface Builder files unless they are referenced as NSLocalizedStrings in the code, potentially leading to incomplete audits.

Question 5

What Python version do I need for nslocalizer?

Accepted Answer

It requires Python 3.5.0 or higher, along with specific modules like pbPlist and pyobjc-core, as listed in the requirements section of the README.

Question 6

Is nslocalizer actively maintained and reliable?

Accepted Answer

The README shows badges for Code Climate and CircleCI, suggesting some maintenance, but check the GitHub repository for recent commits and issue activity to assess current reliability.

nslocalizer

What is nslocalizer?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions