Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/ovolab/fastlane-plugin-ovo_poeditor/llms.txt

Use this file to discover all available pages before exploring further.

The file_format parameter controls both what the plugin requests from the POEditor export API and how the resulting files are arranged on disk. Choosing the correct format for your project avoids misplaced files and ensures the platform’s string-loading machinery finds everything it expects. Three formats are supported: xcstrings for modern Xcode 15+ Swift String Catalogs, apple_strings for traditional .strings files used by UIKit and AppKit projects, and android_strings for Android XML resource files.

xcstrings

The Swift String Catalog format was introduced in Xcode 15. Rather than one file per language, all translations for every language in the project are bundled into a single JSON-based .xcstrings file. Xcode reads this file at build time and provides the correct translation for the active locale automatically.POEditor export type sent: xcstringsAdditional options sent to POEditor API: options: [{"export_all":1}]This export_all option tells POEditor to include every project language in the exported file, regardless of which language code you pass in languages. As a result, you only need to provide a single language entry in the languages array — the plugin still iterates over it to trigger the export call, but the resulting file contains all languages.Output path formula:
{output_dir}/{file_name}
The output is written to a single flat path — there is no language subfolder. All languages share one file.Example output path:
./XCStrings/Localizable.xcstrings
Fastfile example:
Fastfile
ovo_poeditor_strings(
  api_token: ENV["POEDITOR_API_TOKEN"],
  project_id: ENV["POEDITOR_PROJECT_ID"],
  languages: ["en"],
  output_dir: "./XCStrings",
  file_format: "xcstrings",
  file_name: "Localizable.xcstrings"
)
Parameters that apply to this format:
ParameterUsed
api_token
project_id
languages✅ (single code sufficient)
output_dir
file_name
file_format
fallback_languages
default_language❌ ignored
language_map❌ ignored
unquoted_strings❌ ignored
bypass_default_language❌ ignored
For a complete walkthrough, see iOS xcstrings Guide.

Choosing a Format

Use the table below to select the right format for your project type.
FormatBest forXcode / Gradle version
xcstringsModern Swift projects using Xcode’s String Catalog featureXcode 15 and later
apple_stringsUIKit, AppKit, or SwiftUI projects targeting older Xcode versionsXcode 14 and earlier, or any version with existing .strings workflows
android_stringsAndroid Gradle projects using standard XML string resourcesAny Android Gradle version
  • Choose xcstrings for any Xcode 15+ project. The single-file output simplifies your repository and gives Xcode full control over pluralisation and locale fallbacks.
  • Choose apple_strings if your project predates Xcode 15, uses a custom localization build step, or already has an established .lproj directory structure you want to preserve.
  • Choose android_strings for any Android project. Combine it with default_language and language_map to match your module’s exact resource directory naming conventions. See Language Mapping for details.

Build docs developers (and LLMs) love