We recently made a list of all the formats we support for localization projects, and gave a few explanations for each of them, linked to POEditor’s expectations. We take the chance to clarify a question that keeps popping up in our mailbox: why do we not support certain formats?
The short answer is because of the perspective from which we’ve built the entire translation platform: we preferred to treat every localization job from a project point of view, and not as a mere file translation. For this reason, we need to be able to import every localization file format to the same list of terms and translations, so we can provide back to our users the same content, in the same format, flawlessly.
Taking this into consideration, and the fact that we don’t like to “partially support” language files, we’ve arrived at this list of main formats.
The current list of formats is not final, of course, and new additions will be adapted to this vision, so our users won’t get the feeling of getting too technical.
Have a look at our supported formats:
Gettext .po and .pot files, Excel .xls and .xlsx files, Android .xml files, Apple .strings, Microsoft .resx and .resw files, Java .properties files, .json text files.