To translate an INI file, import it into a POEditor project as your source language, translate the strings with AI, machine translation or your own translators, then export each language as a localized .ini file. Here's how to set it up.
1. Create a localization project
Log in to your POEditor account, click on Add New Project and add your software's source language to it.
2. Import strings from your INI file
In the project page, click on Import to upload the strings from your INI file. Choose Also import translations to a language and select the source language you added in step 1.
Set this language as your project's Default Reference Language after you import the translations. You can change the Default Reference Language in the project's Settings.
3. Translate into your target languages
Add the languages you want, then choose how to translate them:
- AI translation with your own OpenAI, Claude, Gemini, Azure AI or Amazon Bedrock account. You can customize the prompt to match your tone.
- Machine translation with Google Translate, DeepL or Azure AI Translator.
- Your own translators, invited as contributors to specific languages.
- Human translations, ordered from the available LSPs.
Translation memory (available from the Start plan) suggests earlier translations of similar strings, and QA checks and QE feature catch issues before export.
Click Export in any translation page to download that language as an .ini file, or use one of the other export options.
If you want to automate the import/export, use the POEditor API, one of the integrations with code hosting platforms or Workflows.