Understand the machine-translation integration boundary
POM Translate supports machine translation through POM AI. It does not expose a public provider-adapter interface, a filter for replacing the provider client, or a setting for an arbitrary translation service.
The supported division of responsibilities is:
- POM Translate discovers source strings, groups background work, validates protected placeholders, records workflow statuses, and stores accepted translations.
- POM AI authorizes the service request and produces the candidate translations.
- Editors remain responsible for reviewing wording, links, formatting, and business-critical terminology.
Choose the appropriate integration
Use the built-in POM AI workflow when a site needs machine-assisted drafts inside the normal translation queue.
Use the public registration helpers when another plugin owns stable visitor-facing strings that should become available to POM Translate.
Use the JSON import workflow when translations are prepared in an external editorial system. The import format is a supported exchange point; the private POM AI transport is not.
Do not write directly to POM Translate tables or replace internal classes. Those approaches bypass source matching, placeholder checks, statuses, cache invalidation, and future compatibility.
Continue with Stay inside the supported boundary, then review Prepare safe source material and Validate machine-translated output.