Convert PO to JSON

Turn PO files into JSON. JSON for agents with the source and target languages and one object per entry holding its context, source and plural source, translation or plural forms, state, notes, comments, source references, flags and an obsolete mark.

Converted in an isolated sandbox on our serversDeleted after 24 hours

Drop PO files on the dialor turn it to pick what to do

Every message in one JSON file.Each entry keeps its context, source text, translation and notes.

  1. What you get

    One JSON file for the whole catalog. It lists the source and target languages, then one object per entry.

    Each entry object holds its context, source and plural source, and its translation or plural forms. It also holds the entry's state, notes, comments, source references and flags, and an obsolete mark.

  2. What the entries hold

    Plural messages carry their plural source and their plural forms in the same object as the rest of the entry. Notes, comments and source references stay with the entry they belong to, so nothing has to be matched up by hand.

    Both .po files and .pot templates are accepted as input. The output is one file either way.

  3. Next steps

    The JSON is built for agents, with every part of an entry in its own named place. To combine this file with others, see merge JSON. For other JSON outputs, see every JSON conversion.

PO and JSON.What each format is.

The formats

From · PO

Gettext PO

Gettext translation catalogs and .pot templates, with each message's context, plural forms, notes and fuzzy mark.

Extensions
.po .pot
MIME type
text/x-gettext-translation
Kind
Text and data
To · JSON

JSON

JSON, the data format of every API.

Extensions
.json
MIME type
application/json
Kind
Text and data

In your code.The same PO to JSON conversion through the API, for your app or your agent.

terminal
$ cv convert report.po report.json
$ cv convert report.po report.json

Questions.What people ask about PO to JSON.

01OF 04

Each entry holds its context, source and plural source, translation or plural forms, state, notes, comments, source references, flags and an obsolete mark.

Yes. PO covers both .po catalogs and .pot templates.

Yes. The JSON lists the source and target languages along with the entries.

One file. The whole catalog goes into a single JSON file.

More conversions.Other ways in and out of PO and JSON.