How do I set up BartyCrouch in an Xcode build script?

Add a new run script phase in Xcode's Build Phases tab with commands like 'bartycrouch update -x' and 'bartycrouch lint -x', then move it before compiling sources. This ensures strings are updated automatically on each build, as detailed in the README's Build Script section.

BartyCrouch vs Apple String Catalogs: which is better?

For new projects on Xcode 15 or later, String Catalogs are recommended because they're built-in, Apple-supported, and cover most BartyCrouch features except machine translation. BartyCrouch is useful if you need machine translation or are stuck on older Xcode versions, but the author advises migrating to String Catalogs and using TranslateKit for translation.

Can BartyCrouch handle localization for SwiftUI apps?

BartyCrouch is optimized for UIKit/AppKit with Storyboards and code using NSLocalizedString. It doesn't directly extract strings from SwiftUI views, so you may need manual management or other tools for SwiftUI-specific localization, limiting its effectiveness in modern SwiftUI projects.

How accurate is the machine translation in BartyCrouch?

It uses Microsoft Translator or DeepL APIs, which are decent for draft translations but can miss nuances and context. It's best for generating initial translations that should be reviewed by humans, especially for user-facing or critical text.

What does it cost to use BartyCrouch's translation feature?

BartyCrouch itself is free, but machine translation requires subscription keys from Microsoft Translator or DeepL, which may have usage-based costs. You'll need to sign up for these services and manage API keys, adding potential expenses.

How do I ignore certain strings so BartyCrouch doesn't update them?

Add '#bc-ignore!' in the comment of NSLocalizedString calls or in Interface Builder values. This tells BartyCrouch to skip those strings during updates, useful for programmatically set strings or those handled in .stringsdict files for pluralization.

Is BartyCrouch still being actively developed?

The README states it's kept up-to-date only by volunteers, with the author focusing on TranslateKit. While it receives occasional updates, active development has slowed, so consider this for maintenance and future-proofing in long-term projects.

Open-Awesome

BartyCrouch

MITSwift4.15.1

Incrementally update and translate iOS/macOS app Strings files from Swift, Objective-C, Storyboard, and XIB files.

GitHub

1.4k stars116 forks0 contributors

What is BartyCrouch?

BartyCrouch is a command-line tool for iOS and macOS developers that automates the extraction and management of localization strings. It incrementally updates `.strings` files from Swift, Objective-C, Storyboard, and XIB files, preserving existing translations and comments. It also supports machine translation and integrates into Xcode build scripts to streamline the localization workflow.

Target Audience

iOS and macOS developers working on apps that require localization, especially teams managing multiple languages or large codebases where manual string updates are error-prone.

Value Proposition

Developers choose BartyCrouch for its incremental update approach that avoids overwriting translations, its integration with Xcode builds, and support for machine translation—reducing manual effort and keeping localization files in sync with code changes.

Overview

Localization/I18n: Incrementally update/translate your Strings files from .swift, .h, .m(m), .storyboard or .xib files.

Use Cases

Best For

Automatically extracting new strings from Swift and Objective-C code into Localizable.strings
Keeping Storyboard and XIB string files synchronized with interface changes
Translating app content into multiple languages using machine translation APIs
Linting localization files for duplicate keys and empty values in CI pipelines
Integrating localization updates into Xcode build scripts for continuous synchronization
Managing large localization projects with many languages and frequent string additions

Not Ideal For

Projects already using or planning to migrate to Xcode 15's built-in String Catalogs, which offer similar incremental updates without external tooling.
Teams requiring high-accuracy, human-reviewed translations without relying on imperfect machine translation APIs.
Developers working primarily with SwiftUI or newer Apple frameworks where String Catalogs provide better native integration.
Apps with minimal localization needs or infrequent string changes, where the configuration overhead outweighs the benefits.

Pros & Cons

Pros

Incremental Update Safety

Preserves existing translations and comments when adding new keys from code and Interface Builder files, preventing data loss and manual rework.

Build Script Automation

Integrates into Xcode build phases to run automatically on each build, ensuring localization files stay synchronized with code changes seamlessly.

Machine Translation Integration

Supports translation into 60+ languages via Microsoft Translator or DeepL APIs, automating initial translations and reducing manual effort for multi-language apps.

Code Transformation Workflow

Replaces BartyCrouch.translate calls with NSLocalizedString or SwiftGen L10n calls during build, streamlining Swift localization without leaving the code editor.

Cons

Complex Configuration Burden

Requires detailed setup of a .bartycrouch.toml file and potential code modifications, which can be time-consuming and error-prone for new users.

External API Dependencies

Machine translation features depend on third-party subscription keys (e.g., Microsoft Translator), adding cost and external reliance that may not suit all teams.

Declining Relevance

The README explicitly recommends migrating to Apple's String Catalogs in Xcode 15, as BartyCrouch misses built-in support and is maintained only by volunteers, reducing long-term viability.

Limited SwiftUI Support

Primarily designed for UIKit/AppKit with Storyboards and XIBs, lacking direct integration for SwiftUI's localization patterns, which may require workarounds.

Frequently Asked Questions

Related Projects

Localize-Swift

Swift friendly localization and i18n with in-app language switching

Stars3,126

Forks328

Last commit2 years ago

LocalizationKit

Realtime Dynamic localization translation delivery system for iOS and Mac OSX in Swift. Create and update texts from localization.com without needing to recompile or redeploy. Cocapod for iOS devices (iPad, iPhone, iPod Touch and Mac)

Stars1,211

Forks78

Last commit6 years ago

Swifternalization

Localize iOS apps in a smarter way using JSON files. Swift framework.

Stars574

Forks46

Last commit3 years ago

Hodor

Simple solution to localize your iOS App.

Stars540

Forks56

Last commit7 years ago

Community-curated · Updated weekly · 100% open source

Found a gem we're missing?

Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.

Submit a project Star on GitHub