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.

How does it handle ISO-8859-1 vs UTF-8?

i18n Agent detects the encoding of your source file. For ISO-8859-1 files, non-Latin characters are converted to \uXXXX escape sequences. For UTF-8 files, native Unicode characters are written directly.

Will escape sequences be preserved?

Yes. All Java .properties escape sequences — including \n (newline), \t (tab), \\ (backslash), \= (equals), and \: (colon) — are detected and preserved unchanged.

Are comments preserved?

Yes. Comment lines starting with # or ! are preserved in their original positions. Section headers and developer documentation remain intact.

Does it handle multiline values?

Yes. Continuation lines (values split with trailing backslash) are recognized and handled correctly. The multiline structure is preserved in the output.

Does it work with Spring Boot message bundles?

Yes. i18n Agent handles Spring Boot's messages.properties convention, including MessageFormat patterns with {0}, {1} placeholders and choice format expressions.

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 .properties Files Without Encoding Headaches

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

Encoding handled. Escape sequences preserved. Comments intact. Unicode escapes correct. Your properties files translated without the ISO-8859-1 pain.

.properties Translation Is an Encoding Nightmare

Java .properties files have a 30-year legacy of encoding quirks. The default encoding is ISO-8859-1, non-Latin characters must use Unicode escape sequences (\uXXXX), and escape rules for backslashes, newlines, and special characters trip up every generic translation tool.

ISO-8859-1 vs UTF-8 encoding mismatch corrupts non-Latin characters — Japanese, Chinese, and Korean text becomes garbage

Backslash escape sequences (\n, \t, \\, \=) get double-escaped, stripped, or treated as literal text

Comment lines (# and !) and inline comments are stripped, losing developer context and section organization

Unicode escape sequences (\uXXXX) for non-Latin characters get corrupted, translated, or converted incorrectly

Source (English)

messages_en.properties

# Application messages
# Generated by Spring Boot i18n

app.title=My Application
app.description=A powerful tool for your team

# Navigation
nav.home=Home
nav.settings=Settings
nav.logout=Log Out

# User messages
user.greeting=Hello, {0}!
user.welcome=Welcome back, {0}. You have {1} new notifications.

# Special characters and unicode
currency.format=${0,number,#,##0.00}
path.separator=C:\\Users\\Documents
special.chars=Line one\nLine two\nLine three
unicode.example=\u00E9\u00E8\u00EA

Translated (Japanese)

messages_ja.properties

# Application messages
# Generated by Spring Boot i18n

app.title=Meine Anwendung
app.description=Ein leistungsstarkes Werkzeug f\u00FCr Ihr Team

# Navigation
nav.home=Startseite
nav.settings=Einstellungen
nav.logout=Abmelden

# User messages
user.greeting=Hallo, {0}!
user.welcome=Willkommen zur\u00FCck, {0}. Sie haben {1} neue Benachrichtigungen.

# Special characters and unicode
currency.format=${0,number,#,##0.00}
path.separator=C:\\Users\\Dokumente
special.chars=Zeile eins\nZeile zwei\nZeile drei
unicode.example=\u00E9\u00E8\u00EA