How to set up BartyCrouch to run automatically in Xcode?

Add a run script phase in your target's Build Phases with the provided shell script from the README that checks for BartyCrouch installation and runs update and lint commands with -x for Xcode output. This ensures localization updates on every build.

BartyCrouch vs Xcode 15 String Catalogs: which is better for iOS apps?

For new projects on Xcode 15+, String Catalogs are recommended as they are native, backward-compatible, and handle incremental updates. BartyCrouch is better for legacy projects or if you need machine translation, but the author advises migrating to String Catalogs and using TranslateKit for translation gaps.

Can BartyCrouch handle pluralization in localized strings?

BartyCrouch can ignore strings marked with #bc-ignore! for use with .stringsdict files for pluralization, but it doesn't directly manage pluralization; you need to handle it separately in your code, as mentioned in the exclusion examples.

How to ignore specific strings in Interface Builder with BartyCrouch?

Include #bartycrouch-ignore! or #bc-ignore! in the value or comment field of the view in Interface Builder, or in the comment of NSLocalizedString calls, as shown in the README's exclusion section.

Does BartyCrouch work with SwiftUI localization?

BartyCrouch works with LocalizableStringResource types for AppIntents, but it requires marking strings explicitly with LocalizedStringResource and configuring customFunction in the code task, as detailed in the README. Direct SwiftUI integration may need manual adaptation.

How to migrate from BartyCrouch to Xcode String Catalogs?

Right-click on your .strings files in Xcode 15+ and select 'Migrate to String Catalog...'. The author provides a detailed FAQ for this, and you can use TranslateKit for machine translation if needed, as BartyCrouch's translation feature isn't native to String Catalogs.

Open-Awesome

BartyCrouch

MITSwift4.15.1

A command-line tool to incrementally update and translate iOS/macOS localization strings from Swift, Objective-C, and Interface Builder files.

GitHub

1.4k stars116 forks0 contributors

What is BartyCrouch?

BartyCrouch is a command-line tool for iOS and macOS developers that automates the management of localization strings. It extracts strings from Swift, Objective-C, and Interface Builder files, updates `.strings` files incrementally, and can integrate machine translation to fill missing translations. It solves the problem of keeping localization files in sync with code changes manually.

Target Audience

iOS and macOS developers working on apps that support multiple languages and need to maintain `.strings` files efficiently. It's particularly useful for teams with frequent UI or copy changes.

Value Proposition

Developers choose BartyCrouch for its incremental update approach that preserves existing translations, its ability to automate localization via build scripts, and its support for both code and Interface Builder files—reducing manual effort and errors in the i18n process.

Overview

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

Use Cases

Best For

Automating localization updates in Xcode projects
Extracting strings from Swift and Objective-C code
Keeping Interface Builder (.storyboard/.xib) strings synchronized
Integrating machine translation into the development workflow
Linting `.strings` files for duplicates and empty values
Replacing custom translation calls with `NSLocalizedString` or SwiftGen `L10n` automatically

Not Ideal For

Projects already using Xcode 15's native String Catalogs for localization
Teams heavily reliant on Objective-C code wanting to use the automated transform feature
Apps requiring advanced string formatting or pluralization support beyond basic .strings files
Organizations needing cloud-based or real-time collaborative translation workflows

Pros & Cons

Pros

Incremental Update Preservation

BartyCrouch updates .strings files incrementally, preserving existing translations and comments, which prevents data loss during automation as highlighted in the README's core description.

Multi-Source String Extraction

It extracts strings from Swift, Objective-C (.swift, .h, .m), and Interface Builder files (.storyboard, .xib), covering both code and UI elements for comprehensive localization.

Machine Translation Integration

Supports Microsoft Translator and DeepL APIs to auto-translate missing strings, streamlining the translation process with configurable tasks in the .bartycrouch.toml file.

Build Script Automation

Can be integrated into Xcode build phases via a run script, ensuring localization updates and linting happen automatically on each build, reducing manual effort.

Cons

Limited Transform Support

The transform task does not support formatted localized strings as of version 4.x, and it only works with Swift code, excluding Objective-C, which limits its utility in mixed-language projects.

Reduced Active Maintenance

The README notes that BartyCrouch is now maintained by volunteers, with the original author recommending migration to Xcode 15's String Catalogs, indicating potential future instability or lack of updates.

Configuration Complexity

Setting up requires creating and fine-tuning a .bartycrouch.toml configuration file with specific paths and options, which can be error-prone and time-consuming for large projects.

Frequently Asked Questions

Related Projects

Localize-Swift

Swift friendly localization and i18n with in-app language switching

Stars3,128

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,213

Forks78

Last commit6 years ago

IBLocalizable

Localize your views directly in Interface Builder with IBLocalizable

Stars454

Forks46

Last commit3 years ago

L10n-swift

Localization of the application with ability to change language "on the fly" and support for plural form in any language.

Stars325

Forks31

Last commit1 year 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