Use Polyglot with your existing stack
Keep catalog ownership explicit. You can evaluate supported Polyglot checks while your current translation service continues publishing.
Check the runtime and catalog format
Identify the app root, i18n library, source and target paths, key conventions, plural syntax, and locale loader. Framework detection alone does not establish compatibility. Review the support matrix before applying or importing changes.
Check your runtime and catalogs
Choose one writer for each catalog scope
Record the exact paths and languages, the publishing system, review owner, and merge owner. Two automated systems must not independently write the same target catalog scope.
| Scope | Who writes | Who approves / merges |
|---|---|---|
| Source catalog paths and language | Engineering through feature PRs | Repository maintainers |
| Target catalog paths and languages | Existing service OR Polyglot Publisher | Language reviewer, then repository maintainer |
| Runtime wiring and release | Engineering | Engineer verifies; release owner ships |
1. Keep your translation service authoritative
Use supported local scanning, reviewed wrapping, and self-managed checks. Keep Polyglot Publisher disabled for catalogs owned by your current service. Review any proposed source-catalog changes against that service’s extraction and sync process.
2. Evaluate an independently owned scope
Choose a separate supported project or catalog scope whose files and languages your existing service does not write. Confirm the actual configuration supports that separation. If it cannot, use a reference repository or a diagnostics-only evaluation first.
3. Transfer publication deliberately
- Save a baseline of source and target catalogs, current sync configuration, and a working screen.
- Check preservation of existing keys, reviewed values, placeholders, plurals, and locale loading on a small scope.
- Disable competing target-catalog writers before enabling Polyglot Publisher. Agree who reviews and who merges.
- Complete one reviewed catalog PR and a subsequent copy update. Merge, resync, and exercise the screen after each.
- To return ownership, pause Polyglot publication, reconcile or revert its changes, then restore the previous service’s writer and verify the result.
This workflow does not imply native Crowdin, Lokalise, or Tolgee connectors, universal catalog import, or automatic namespace isolation.