Tour the Translation Manager
Open Translations in WordPress administration. Access to the screen requires permission to manage translations; the Software translations tab has a separate, higher-privilege check.
Main tabs
| Tab | Purpose |
|---|---|
| Translate contents | Edit extracted post, metadata, term, and menu strings |
| Other translations | Edit registered defaults, date formats, and WooCommerce email text |
| Translate URLs | Manage content slugs and custom-link translations |
| Translation exclusions | Exclude posts, terms, or menu items by target language |
| Software translations | Load a gettext text domain and export PO or MO files |
| Generate pending translations | Run a complete content scan or translate only unresolved stored strings |
Software translations appears only for users allowed to manage software catalogs. By default, this requires the WordPress manage_options capability.
Language navigation
The content, defaults, custom-link, and software views display language choices appropriate to that tool. Content and defaults target additional languages. Software catalogs can include the base locale because they are external gettext files rather than POM Translate database rows.
Changing the active language affects the current editor view only. It does not limit Generate pending translations, which processes every configured additional language.
Translation states
Database-backed string tables use four statuses:
- Pending: unresolved or intentionally returned to the machine-translation workflow;
- Machine: saved by automatic translation;
- Human: entered or changed by an editor;
- Reviewed: explicitly marked as reviewed.
The tables support search, status filters, and bulk status changes. Delete selected translations removes the selected locale's translations, not their source strings.
Continue with Choose a language and understand scope before running the generator.