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.

Will my YAML indentation be preserved?

Yes. i18n Agent parses YAML structurally, not as plain text. The output matches your source file's indentation style exactly.

Does it handle YAML anchors and aliases?

Yes. Anchors (&name) and aliases (*name) are recognized as YAML syntax, not translatable content. They pass through untouched.

What about multi-line strings with block scalars?

Block scalars (|, >, |-) are fully supported. The content is translated while the scalar indicator and indentation are preserved.

Does it work with Rails i18n YAML files?

Yes. Rails i18n YAML format is natively supported, including nested locale keys, pluralization rules, and interpolation variables.

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 YAML Files Without Breaking Indentation

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

Anchors preserved. Multi-line strings intact. Comments kept. Your YAML structure comes back exactly as it went in, just translated.

YAML Translation Is Fragile by Design

YAML is whitespace-sensitive. One wrong indent and your entire config breaks. Generic translation tools don't understand YAML's anchors, multi-line strings, or flow scalars, and they certainly don't preserve them.

A single space off and your YAML is invalid. Generic tools don't respect indentation rules.

YAML anchors (&anchor) and aliases (*anchor) get treated as translatable text

Multi-line strings (|, >, |-, >-) lose their block scalar formatting

Comments are stripped or moved, losing developer context

Source (English)

config/locales/en.yml

en:
  welcome: "Welcome, %{name}!"
  products:
    title: "Our Products"
    empty: "No products found"
  errors:
    not_found: "Page not found"
    server: |
      Something went wrong.
      Please try again later.

Translated (Japanese)

config/locales/ja.yml

ja:
  welcome: "ようこそ、%{name}さん！"
  products:
    title: "製品一覧"
    empty: "製品が見つかりません"
  errors:
    not_found: "ページが見つかりません"
    server: |
      問題が発生しました。
      後でもう一度お試しください。