Multilingual Plugins

Oxygen doesn't translate your site. Translation is what multilingual plugins do, and Oxygen
is designed to stay out of their way rather than ship an integration for each one.

What Oxygen users use

These are the solutions Oxygen users report the most success with. None of them is built by
us, and none is bundled:

• TranslatePress — the most popular choice among Oxygen users, and the one Oxygen ships
  a small compatibility fix for (see below).
• Polylang — reported working by a number of users.
• Weglot — a hosted translation service, and the one we'd suggest looking at first if
  you want translation to be somebody else's problem.

Oxygen contains one piece of multilingual-specific code: on TranslatePress's translation
editor screen, Oxygen steps back and lets WordPress render the page normally, so
TranslatePress can walk the output and collect strings. Everything else works because Oxygen
renders ordinary WordPress content and ordinary HTML.

Note: the quality of these plugins, and of their integrations with Oxygen, isn't
guaranteed or warranted by the Oxygen team, and we can't offer support for problems caused
by third-party multilingual plugins.

Why we don't build these integrations

It isn't reluctance to do the work — it's that an integration we maintain is the wrong place
for this to live:

• Multilingual plugins ship hundreds of releases a year, and any of them can break an
  integration written against the previous one.
• Much of what an integration has to hook into is undocumented internals, which change
  without notice.
• Every hour spent chasing those changes is an hour not spent on the builder.
• Multilingual plugin developers already build and maintain their own integrations with
  every major builder. They're better placed to do it, because they know what their own
  plugin needs.

What we do instead

We support the developers who build these integrations:

• APIs. WordPress provides the APIs plugins talk to each other through, and we'll extend
  ours where an integration needs something specific.
• Hooks and filters. Oxygen exposes action hooks and filters across the builder and the
  render path, and we add more when an integration has a real use for them.
• Direct help. We'll work with a multilingual plugin's development team on their Oxygen
  integration.

If you want your multilingual plugin to work better with Oxygen, telling its developers
you use Oxygen is the single most effective thing you can do. That demand is what puts an
integration on their roadmap — and we'll help them build it when it gets there.