Skip to content

PO export and import

These commands are for interoperability with PO/CAT workflows. They are not the canonical RimLoc project model and are not required when you translate directly in the desktop application.

Export PO

Use export-po when you want a single PO handoff for Poedit, another CAT tool, or an external translator.

rimloc-cli export-po \
  --root ./Mods/MyMod \
  --out-po ./work/MyMod.ru.po \
  --lang ru

Useful options in current builds include:

  • --source-lang / --source-lang-dir;
  • repeatable --tm-root for legacy/root-based translation reuse;
  • --game-version;
  • --include-all-versions.

Run source validation before handoff:

rimloc-cli validate --root ./Mods/MyMod

Validate PO

rimloc-cli validate-po --po ./work/MyMod.ru.po --strict

This catches handoff-level issues such as placeholder mismatches.

Import PO

Import can target a single XML file or a copied/mod working tree.

Preview first:

rimloc-cli import-po \
  --po ./work/MyMod.ru.po \
  --mod-root ./work/MyMod-copy \
  --lang ru \
  --dry-run \
  --report

Then rerun without --dry-run only after the plan is correct.

Common controls include:

  • --backup;
  • --incremental;
  • --only-diff;
  • --single-file;
  • --format text|json.

Do not import into Workshop originals

The current product direction treats game/Workshop/source directories as read-only. For manual CLI experiments, use a working copy or isolated output tree.

Not using PO?

That is normal.

  • Desktop project editing does not require PO.
  • build-mod --from-root can package an existing translated Languages tree.
  • Future/other interchange formats should remain adapters around the same canonical project model.

See Build Mod and Getting started.