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 plural forms for different languages?

i18n Agent knows the correct nplurals and plural formula for each language. Japanese gets nplurals=1, Russian gets nplurals=3, Arabic gets nplurals=6. The PO header is updated automatically.

Can I translate POT template files directly?

Yes. Provide a POT file as source, and i18n Agent generates properly formatted PO files for each target language with correct headers and plural forms.

Does it respect msgctxt for disambiguation?

Yes. When the same msgid appears with different msgctxt values, each is translated independently based on its context.

Does it work with WordPress translation files?

Yes. WordPress PO/MO format is natively supported. You can translate PO files and compile to MO for WordPress deployment.

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 PO Files Without Losing Plural Forms

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

msgid intact. Plural forms correct for every language. Comments preserved. Your gettext workflow, but faster.

PO Translation Tools Ignore What Makes PO Special

PO files aren't just key-value pairs. They have plural forms that vary by language, message contexts for disambiguation, translator comments, and source references. Most translation tools treat them like flat text files.

nplurals and plural formulas differ by language. Generic tools use wrong plural counts.

msgctxt disambiguation context gets ignored or translated

Translator comments (#.) and source references (#:) are stripped

Character encoding headers and PO metadata get corrupted

Source (English)

messages.pot

#: src/components/Cart.tsx:42
#. Translator: shown when cart is empty
msgid "Your cart is empty"
msgstr ""

#: src/components/Cart.tsx:55
msgid "item"
msgid_plural "items"
msgstr[0] ""
msgstr[1] ""

#: src/components/Auth.tsx:12
msgctxt "button"
msgid "Sign in"
msgstr ""

Translated (Spanish)

es/LC_MESSAGES/messages.po

#: src/components/Cart.tsx:42
#. Translator: shown when cart is empty
msgid "Your cart is empty"
msgstr "Tu carrito está vacío"

#: src/components/Cart.tsx:55
msgid "item"
msgid_plural "items"
msgstr[0] "artículo"
msgstr[1] "artículos"

#: src/components/Auth.tsx:12
msgctxt "button"
msgid "Sign in"
msgstr "Iniciar sesión"