Convert STRINGS to PO
Turn STRINGS files into PO. A gettext PO file with each entry's context, source text and plural source, translation or plural forms, notes, translator comments, source references, flags and fuzzy mark, obsolete entries as #~ lines, and a header with the language and its plural rule.
Converted in an isolated sandbox on our serversDeleted after 24 hours
Drop STRINGS files on the dialor turn it to pick what to do
Strings in, a PO catalog out.Each string lands in a gettext PO file with its header and notes.
What you get
One PO file that holds the strings from your Apple Strings file. Each entry carries its source text and its translation. Plural entries carry the plural source and the plural forms.
The file starts with a header that names the language and its plural rule.
What goes into each entry
Each entry keeps its context, notes, translator comments and source references. Flags are written too, along with the fuzzy mark, so entries that still need review stay marked.
Obsolete entries are written as #~ lines.
STRINGS and PO.What each format is.
The formats
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
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
In your code.The same STRINGS to PO conversion through the API, for your app or your agent.
$ cv convert report.strings report.po$ cv convert report.strings report.poQuestions.What people ask about STRINGS to PO.
It holds a header with the language and its plural rule, then the entries. Each entry has its source text, its translation or plural forms, and its context, notes, comments, references and flags.
Yes. The fuzzy mark is written on the entry along with its other flags.
They are written with the plural source and the plural forms. The plural rule in the header says how the forms are used.
They are written as #~ lines.