Prepare safe source material for machine translation

Developers influence machine-translation quality by registering only stable visitor-facing text and by providing useful, non-sensitive context. The private service request is managed by POM Translate and is not a public integration contract.

Before a value enters the workflow:

• keep user-specific values separate from the stable sentence that surrounds them;
• preserve placeholders used for names, amounts, URLs, HTML, or shortcode data;
• avoid sending technical identifiers, serialized values, credentials, or markup-only fragments;
• register a stable name and context for standalone strings;
• add translator notes only when they clarify tone or terminology.

For example, register Your order is ready as a stable string. Do not register a completed message containing a customer's name and order number.

POM Translate groups eligible source strings for the destination locale and validates protected markers before it accepts a result. Custom code should not pre-concatenate unrelated values merely to create a larger batch.

Verify a new integration with one short string, one formatted string, and one value containing the placeholders that the real content uses. Confirm that all three remain editable and render correctly after translation.