What file formats does i18n Agent support?

i18n Agent supports 9+ file formats including JSON, YAML, CSV, XML, Markdown, Properties, and more. The service preserves structure and formatting automatically.

How much does i18n Agent cost?

i18n Agent costs €0.01 per word, which is significantly more affordable than traditional translation services that typically charge €0.15-0.25 per word.

What is MCP integration?

MCP (Model Context Protocol) integration allows i18n Agent to work directly with AI development tools like Claude Code, Cursor, and other AI-powered development environments for seamless translation workflows.

Does it support both .strings and .stringsdict files?

Yes. i18n Agent handles both Localizable.strings (key-value pairs) and Localizable.stringsdict (plural rules) files. Xcode 15 String Catalogs (.xcstrings) are also supported.

Will my format specifiers be preserved?

Yes. i18n Agent detects all Apple format specifiers including %@, %d, %f, positional variants like %1$@, and width/precision modifiers. They are never translated or reordered.

How does it handle plural rules?

Stringsdict files use CLDR plural categories. i18n Agent generates the correct categories for each target language. Japanese gets 'other' only, while Arabic gets all six categories.

Does it support Xcode 15 String Catalogs?

Yes. The .xcstrings JSON format is fully supported. Keys, plural variations, and device-specific strings are all handled correctly.

How accurate are the translations?

i18n Agent uses a multi-model AI pipeline with built-in quality scoring. Each translation passes through technical accuracy verification, cultural adaptation, and consistency validation before delivery.

How much does it cost?

No monthly fee. You pay €0.01 per source word, per target language. Typical files cost a few euros to translate.

Translate .strings Files Without Breaking Your App

Name: i18n Agent
Price: 0.01 EUR
Rating: 4.8 (127 reviews)
Author: i18n Agent

Keys untouched. Format specifiers preserved. Plural rules correct. Your Localizable.strings translated in seconds, not days.

Apple .strings Translation Is Tedious and Error-Prone

You export your Localizable.strings, hand it to a translator or paste it into a generic tool, get back corrupted format specifiers, broken escape sequences, and mangled plural rules. Then you spend hours debugging why your app crashes on launch in Japanese.

Format specifiers like %@, %d, and %1$@ get translated, reordered, or removed by generic tools

Escape sequences (\n, \", \t) get corrupted or double-escaped, breaking string parsing

Stringsdict plural rules need language-specific CLDR categories that most tools ignore entirely

Translator comments and context hints are stripped, leading to wrong translations

Source (English)

Base.lproj/Localizable.strings

/* Localizable.strings (English) */

"welcome_title" = "Welcome to MyApp";
"login_button" = "Sign In";
"greeting" = "Hello, %@!";
"items_count" = "%d items in your cart";
"transfer" = "Send %1$@ to %2$@";

Translated (Japanese)

ja.lproj/Localizable.strings

/* Localizable.strings (Japanese) */

"welcome_title" = "MyAppへようこそ";
"login_button" = "サインイン";
"greeting" = "%@さん、こんにちは！";
"items_count" = "カートに%d個のアイテム";
"transfer" = "%2$@に%1$@を送信";

What i18n Agent Preserves

Format Specifiers

Positional (%1$@) and type-specific (%d, %f, %@) specifiers are detected and left untouched

Escape Sequences

Newlines (\n), tabs (\t), quotes (\"), and Unicode escapes are preserved correctly

Stringsdict Plurals

CLDR plural categories (zero, one, two, few, many, other) are set correctly per target language

Comments & Context

Translator comments and developer notes are preserved to maintain translation context

Works Across Apple Platforms

SwiftUI

UIKit / AppKit

Xcode String Catalogs

macOS Apps

watchOS / tvOS

Swift Packages

Open-Source Tools for iOS Localization

i18n Agent for Xcode

A macOS menu bar app that adds one-click localization to Xcode. It auto-detects your active project, translates your .strings, .xcstrings, and .stringsdict files, and writes them to the correct .lproj directories. Push existing translations as translation memory for consistent results across your project.

Auto-detects your active Xcode project via AppleScript

Pull: translates files and writes to the correct .lproj directories

Push: uploads existing translations as translation memory

Lives in your menu bar, works with .strings, .xcstrings, and .stringsdict

View on GitHub

LocaleChain

iOS has a known gap: when a user's regional locale (like pt-BR) is missing, the system skips straight to English instead of trying a related locale (like pt-PT). LocaleChain is a Swift package that fixes this with configurable fallback chains. One line of setup, zero changes to your existing code.

One-line setup: LocaleChain.configure()

Works transparently with NSLocalizedString, SwiftUI Text, and .stringsdict

Built-in fallback chains for Portuguese, Spanish, French, German, and more

Installs via Swift Package Manager, MIT licensed

View on GitHub