Find and translate registered strings

Use Translations → Other translations to manage standalone strings registered by a theme, plugin, or integration. This view is separate from Software translations, which works with gettext files.

Before you start

• Add at least one additional language.
• Make sure the relevant theme or plugin has run its string registration.
• Open the Translation Manager with an account allowed to translate content.

Registration normally happens when the code path that owns the value loads. A value that has never been registered cannot appear in the list.

Find a value

1. Go to Translations → Other translations.
2. Choose the target locale.
3. Use the status filter if you need only Pending, Machine translated, Human translated, or Reviewed entries.
4. Search for part of the original text or the registered name.
5. Check the context shown for the row.

Registered rows are identified as Registered string. Their field is Custom string, and the context includes the stable registration name when it is available. That name is often the best way to distinguish repeated source text owned by different settings.

Translate the row

1. Enter the translation in the target-locale field.
2. Preserve intentional markup, placeholders, product names, and spacing.
3. Select Save translations.
4. Reload the view and confirm that the value and status remain.
5. Visit the public page in the target language and verify the final output.

When POM AI is enabled, eligible Pending registered strings can also receive a machine-translated draft from this view. Review and save the result before treating it as final.

POM Forms

Saved POM Forms register their text automatically. They share one form across languages and do not have a post-type translation toggle. Search pom/forms/ to find form titles, steps, field labels and help, option labels, HTML blocks, privacy copy, feedback, and notification subjects, sender names, and HTML messages. Search pom/forms/123/ for one form or pom/forms/defaults/ for shared feedback and privacy text.

Newly saved forms register immediately. Existing forms are discovered in background batches after opening WordPress administration. Keep HTML tags and attributes, shortcodes, and merge tags unchanged when translating. A missing translation or one that changes structural markers falls back to the original. Translated labels do not change option values, conditions, recipient addresses, or submitted data.

Client confirmations and administrator notifications use the submitting page's language unless the site's integration chooses another configured language. Programmatically generated forms remain the responsibility of the integration that generates them.

If the string is missing

Confirm that you are in Other translations, not Software translations. Then load the page or feature that registers the value and return to the list.

If the value still does not appear, the integration may be using gettext instead of POM Translate's registration helper, or it may not register that setting at all. A POT/PO/MO message belongs in the software catalog workflow.

Expected result

The saved locale value is stored by POM Translate and replaces the registered original when that integration requests it in the corresponding language. If no locale value exists, visitors continue to see the original.