There are various ways to add strings to a localization project managed with POEditor, both manual and automatic, outlined in this article.
Project page import
The Import option in the project page can be used by project owners, project administrators and organization managers (if the project is hosted on an organization).
You can use the Import option in the project page to upload strings (terms and translations) from any of the supported file formats. A number of options are available:
- Also import translations to a language: uploads the translations in the file to the selected language in the project
- Overwrite existing translations: updates the translations in the project with those in the file
- Mark the corresponding translations from the other languages as fuzzy for the updated values: useful only when updating strings in labels-based projects
- Tags (in Use Advanced Options): help you filter your strings during translation or on export.
For localization file formats like XLIFF, that can contain both the source and target languages, you also have the option to choose which strings to import as translations (from the
<source> tag or
Language page import
This option can be used to add translations to a language by any user with access to that project language, regardless of their role.
The most basic way to import strings to a localization project is by using the Import options in the user interface.
One such option that can be found in every language page. You can use this option to import translations exclusively, from any of the supported file formats.
The language page import allows you to overwrite existing translations.
In order to be able to import translations in a language page, their corresponding terms/keys must've already been imported to the project.
Import via integrations
Project owners and organization managers can set up integrations with Git services and import strings to the project using the UI. They can also set up import webhooks to automate the import process.
Project admins can also manually import strings to POEditor using the links set up by the project owner or organization managers, provided that the integration is shared with them in the project's settings.
In order to automate the strings import, you can use integrations with Git services.
After setting up the integration in the user interface, you can manually import terms (these can be keys/strings ids, depending on your file format) to a project using the Get terms button. To import translations, you can use the Import translations option at the bottom of the integration page.
You can import translations to a localization project only after you've imported the terms.
To keep track of an import, you can tag the imported terms with one or more tags of your liking, using the Add Import Rule option in the link's settings.
To automate the import from your repo to your POEditor project, you can use webhooks with the operations Import new terms, Import translations or Import terms and translations.
The API import can be used with the API key belonging to the user or organization hosting the project, as well as with the API key belonging to the accounts of project admins. The API rates of the account which generated the API key apply.
You can import strings to POEditor with the API using the following methods:
- projects/upload: can import terms, translations, or terms and translations from any of the supported file formats.
- projects/sync: adds new terms from your JSON object and deletes obsolete terms from the POEditor project.
- terms/add: adds terms to the project from a JSON object.
- terms/update: lets you change the terms' text, context, reference, plural and tags.
- languages/update: adds translations to the project where none are specified, and overwrites existing ones with the ones from the JSON object.
- translations/add: adds translations to the project from a JSON object, without overwriting existing ones.
- translations/update: overwrites existing translations with the ones from the sent JSON object.
Importing via plugins
A couple of community-shared plugins are also available, some of which can be used for import.