WordPress / PHP

WordPress speaks gettext — the same .po/.pot catalogs Dialecto is built on. Full WordPress support is on the roadmap; this page states the current boundary so you don’t discover it mid-setup.

What already works

Dialecto’s editing engine is runtime-agnostic gettext: it round-trips any valid PO file byte-faithfully — wrapping, plural forms, obsolete (#~) and previous (#|) entries, every comment kind — and emits one-line-per-change diffs. A WordPress catalog is a valid PO catalog; the engine holds.

What is Elixir-only today

The framework adapter — the layer that understands a runtime’s conventions — has one implementation: Elixir/Phoenix. That adapter owns:

• Path conventions — mapping file paths to locale + domain. WordPress lays catalogs out differently (wp-content/languages/…, text domains) than Phoenix does.
• Usage-snippet extraction — the in-place context shown next to each string, built from the runtime’s gettext call functions (__(), _e(), _x() and friends in WordPress’s case).
• Source call-site rewrite — renaming a key and rewriting the calls.

Because of that, a gettext repository can currently only be registered with the elixir framework — there is no WordPress setup flow yet, and we won’t document one that can’t be completed.

The roadmap

WordPress/PHP is a designed-for runtime: the adapter seam exists precisely so the three concerns above can be implemented per runtime without touching the engine. When the WordPress adapter lands, this page becomes a full guide (setup, scanning, editing, pull-request config) like the Elixir guide.

Want it sooner? Tell us — adapter order follows demand.