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 Android strings.xml format?

Yes. i18n Agent understands the Android resource XML format, including string arrays, plurals, and translatable attributes. Output files are ready to drop into your res/values-xx/ folders.

Can it handle XLIFF files?

Yes. Both XLIFF 1.2 and 2.0 are supported. Source and target elements are correctly populated while preserving notes, context, and state attributes.

Will it translate XML attributes by accident?

No. i18n Agent distinguishes between translatable text content and structural attributes. Only the text values that should be translated are modified.

What about nested tags inside translatable strings?

Inline markup like bold, italic, and link tags within translatable strings are preserved. The text around them is translated while the tags remain intact.

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 XML Files Without Breaking Tags

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

Android strings.xml, XLIFF, RESX, and custom schemas. Tags and attributes stay intact. Just the text content gets translated.

XML Translation Breaks More Than It Fixes

XML looks simple until you need to translate it. Tags get mangled, attributes get translated when they shouldn't be, CDATA sections disappear, and self-closing tags break. One misplaced angle bracket and your entire app crashes.

HTML and XML tags inside translatable strings get corrupted or stripped

Attributes that should stay untouched (IDs, names, formats) get translated by mistake

CDATA sections, processing instructions, and comments are mangled or removed

XML entities and special characters get double-encoded or lost

Source (English)

res/values/strings.xml

<?xml version="1.0" encoding="utf-8"?>
<resources>
    <string name="app_name">MyApp</string>
    <string name="welcome">Welcome, %1$s!</string>
    <string name="items_count">%d items</string>
    <plurals name="inbox">
        <item quantity="one">%d new message</item>
        <item quantity="other">%d new messages</item>
    </plurals>
</resources>

Translated (Korean)

res/values-ko/strings.xml

<?xml version="1.0" encoding="utf-8"?>
<resources>
    <string name="app_name">MyApp</string>
    <string name="welcome">환영합니다, %1$s!</string>
    <string name="items_count">%d개 항목</string>
    <plurals name="inbox">
        <item quantity="other">새 메시지 %d개</item>
    </plurals>
</resources>