Convert PO to CSV
Turn PO files into CSV. A CSV table for translators with the columns context, source, target, form, state, notes, comments and locations: one row per entry, a plural entry spread over rows numbered 0, 1, 2 in the form column, and the state translated, fuzzy or untranslated.
Converted in an isolated sandbox on our serversDeleted after 24 hours
Drop PO files on the dialor turn it to pick what to do
A translation table you can open anywhere.Each message in the catalog becomes one row with its state and notes.
What you get
A CSV table for translators with eight columns: context, source, target, form, state, notes, comments and locations. Each entry in the PO or POT file is one row.
The state column reads translated, fuzzy or untranslated, so you can see which messages still need work.
Plural entries
A plural entry is spread over several rows. The form column numbers them 0, 1, 2, so each plural form has its own row with its own target text.
What it leaves behind
Obsolete entries are dropped. They do not appear in the CSV.
PO and CSV.What each format is.
The formats
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
CSV
Rows of comma-separated values. The plainest way to move a table between programs.
- Extensions
- .csv
- MIME type
- text
/csv - Kind
- Text and data
In your code.The same PO to CSV conversion through the API, for your app or your agent.
$ cv convert report.po report.csv$ cv convert report.po report.csvQuestions.What people ask about PO to CSV.
It has context, source, target, form, state, notes, comments and locations. Each entry in the catalog fills one row.
A plural entry takes several rows. The form column numbers them 0, 1, 2.
Yes. A fuzzy message gets its own row, and the state column says fuzzy. Translated and untranslated messages are marked the same way.
No. Obsolete entries are dropped from the CSV.