AI Glot websiteOpen AI Glot
File formatsOther XML
File formats

Translate other XML files

Translate product feeds, DITA topics, SVG text and other XML up to 12 MB. The plan picks the elements people read, and ids, prices, URLs and attributes stay untouched.

XML that is not an Android resource, a .NET resource, TTML, Qt or XLIFF is read by a generic XML reader: .xml, .svg, .dita and .ditamap files are accepted up to 12 MB. Typical uses are RSS and Google Shopping product feeds, DITA documentation and the labels inside an SVG diagram.

What is translated, and what is left alone

TranslatedLeft as it was
The elements the plan identifies as text for people, shown to you by nameIds, prices, dates and URLs, treated as data
Mixed content, with inline elements kept around the right wordsAttribute values such as href, alt and id, never translated
The words of HTML inside a CDATA blockstyle and script elements, and the CDATA wrapper itself
DITA lists, tables, notes and steps, kept in placeAnything you scope out

Because there is no fixed schema, the plan chooses which elements hold text. Read it before you approve, and correct the choice in your instruction.

What you can ask

A product feed

Translates the copy and leaves the data.

Translate the title and description elements into French. Leave ids, prices, links and availability unchanged.

DITA topics

Keeps lists, tables, notes and steps in place.

Translate the topic text into German, including steps, notes and table cells. Leave product names and element ids unchanged.

Labels in an SVG

Changes the words of a diagram without redrawing a shape.

Translate the text labels into Spanish. Leave the title element unchanged.

HTML inside CDATA

Translates the words and keeps the tags.

Translate the content elements into Italian. Keep the HTML tags inside the CDATA blocks exactly as they are.

An export from another system

Points the plan at the right elements by name.

Translate only the name and notes elements into Portuguese. Do not translate the code or reference elements.

Good to know

  • One target language per upload. If you ask for two, the plan translates one and says so. Run the file once per language: your glossary carries over.
  • Which reader is used. The extension is not enough for .xml: content decides whether a file is Android, .NET, TTML, Qt, XLIFF or generic XML. Those formats have their own guides.
  • Text may not fit. The layout is not adjusted, so a translated label can be wider than its box in an SVG. Skim the result.
  • Attributes are never translated. If an attribute holds words people read, such as an alt text, it will not be written. Move that text into an element, or edit it by hand after.
  • Output filter. Not available: the whole file comes back.
  • Ceiling. 12 MB.

Use these docs with your AI tools

An AI agent can read this documentation directly. You do not need an account or an API key. Everything here is public and read-only.

Query these docs via MCP

Recommended

Add this server to Claude, Claude Code, Cursor, Mistral, or any tool that supports MCP. Your agent can then search AI Glot Docs documentation and read it in full, instead of answering from memory.

https://ai-glot.com/docs/mcp
  • searchFind the passages that answer a question.
  • fetchRead one page in full, as Markdown.
  • list_pagesSee every page in this documentation.

Query these docs over HTTP

The same tools also work as plain web requests. Use this for scripts, or for any tool that does not support MCP. There is one endpoint per tool. Arguments go in the query string, and the answer comes back as JSON.

https://ai-glot.com/docs/api/docs/search?query=custom+domain

Read the OpenAPI description. It is built from the same definitions as the tools, so it always matches what the endpoints do.

Read these docs as Markdown

Add .md to any page URL to get its Markdown source. You can also send the headerAccept: text/markdown to the page URL itself.

To read the whole documentation in one file, open llms-full.txt. For a short index of every page, open llms.txt.