Convert PO to STRINGS
Turn PO files into STRINGS. An Apple .strings file in UTF-8 with one "key" = "value"; line per entry, keyed by the context or else the source text, with notes as comments.
Converted in an isolated sandbox on our serversDeleted after 24 hours
Drop PO files on the dialor turn it to pick what to do
Translation catalogs as an Apple strings file.One line per entry, in the form "key" = "value";, written in UTF-8.
What you get
A single STRINGS file in UTF-8. Each entry is one "key" = "value"; line, as iOS and macOS apps expect in a Localizable.strings file.
The key is the message context when the entry has one. Otherwise the key is the source text. Notes from the PO file become comments in the output.
What changes
Entries without a finished translation keep their source text as the value, so no line is left empty.
Plural entries keep only their first form. The other plural forms are dropped.
For translated entries, the source text is dropped and the translation is the value.
What it leaves behind
Translator comments and source references are not copied. Obsolete entries are dropped too.
PO and STRINGS.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
Apple Strings
Localizable.strings files of iOS and macOS apps, one "key" = "value"; line per string.
- Extensions
- .strings
- MIME type
- text
/x -apple -strings - Kind
- Text and data
In your code.The same PO to STRINGS conversion through the API, for your app or your agent.
$ cv convert report.po report.strings$ cv convert report.po report.stringsQuestions.What people ask about PO to STRINGS.
The message context is the key when there is one. If there is none, the source text is the key.
They keep their source text as the value. The line is still written.
Only the first form is kept. The remaining forms are dropped.
You get one STRINGS file.