Keep software strings separate from content selection

Theme, plugin, and WordPress interface messages do not belong to a post type or taxonomy. The checkboxes under Settings → POM Translate → Content types have no effect on these gettext strings.

Use the correct workspace

Administrators and multisite super administrators can open Translations → Software translations. The workspace asks for a Text domain and a locale, then loads entries from an available POT, PO, or MO source file.

Examples of text domains include:

• default for WordPress core;
• a plugin's declared text domain;
• the active theme's text domain.

Choose the domain, select Load strings, and confirm the reported domain type and source file before editing. If POM Translate cannot find a suitable catalog, it reports that no POT, PO, or MO file was found.

Understand the persistence boundary

Software edits are file-based and are not stored in POM Translate's content-translation database. Leaving the page discards unsaved edits. Use Download PO or Download MO, then install the exported file in a recommended location so WordPress can load it on a later request.

This differs from post, term, menu, and registered-value translations, which use POM Translate's stored content rows.

Decide which mechanism applies

Do not enable extra post types in an attempt to make a plugin button label appear. Find its text domain instead. Continue with Software strings for catalog editing and export.