AI Glot websiteOpen AI Glot
File formatsgettext PO
File formats

Translate gettext PO files

Translate .po and .pot catalogs up to 4 MB entry by entry. Message IDs and contexts stay, plural forms and the Plural-Forms header are written for the target language.

gettext catalogs (.po and .pot) are accepted up to 4 MB. Each msgid keeps its context while its msgstr is filled in. A .pot template has empty entries by definition, so uploading one gives you a .po with them filled in.

What is translated, and what is left alone

TranslatedLeft as it was
msgstr, filled in or redone as you askmsgid and msgctxt, never rewritten
Plural entries: one msgstr per form the target language needs#: references and #. comments
Fuzzy flags, which are kept as they are and not cleared

Plural forms are the part a generic tool gets wrong. The target language decides how many forms exist: Russian and Polish need three, Japanese needs one. The Plural-Forms and Language headers are rewritten to match. A language outside a table of about 65 is left untouched rather than guessed.

What you can ask

Fill the empty entries

Pre-translates a template and leaves reviewed strings alone.

Translate the empty msgstr entries into French. Keep placeholders such as %s, %d and %(name)s unchanged.

Only the changed entries

Returns just the entries that were written, for a small review.

Translate the empty entries into German and return only the entries you changed.

Fuzzy entries

Decides what happens to entries flagged for review.

Redo the fuzzy entries in Spanish, and leave all entries that are not fuzzy as they are.

A WordPress plugin

Keeps the context that tells the same word apart.

Translate this plugin catalogue into Italian. Use the msgctxt to choose the right meaning, and keep HTML tags and placeholders unchanged.

Plurals

Writes every plural form the language needs.

Translate into Polish and write all three plural forms for every plural entry.

Good to know

  • One target language per upload. A catalog holds one language. If you ask for two, the plan translates one and says so. Run the file once per language: your glossary carries over.
  • Output filter. Available. Ask for “only the entries you changed” to get a smaller file back.
  • Fuzzy flags. They are kept as written. Say in your instruction whether fuzzy entries should be redone or left alone.
  • .mo files are compiled catalogs and are refused. Send the .po they were compiled from.
  • Ceiling. 4 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.