Customize localized post objects and output

pom_translate_post_object_localization_fields( array $fields, array $posts, $query, string $locale ) filters which post object fields POM Translate localizes in bulk.

pom_translate_rendered_content( string $rendered, int $post_id, string $locale ) filters reconstructed post content.

pom_translate_should_localize_post_meta_runtime( bool $enabled, int $post_id, string $meta_key, string $locale ) controls runtime metadata localization. pom_translate_translate_prefiltered_post_meta decides whether an already prefiltered value should still be translated.

Use exact field and meta allowlists. Never localize IDs, dates, status, ownership, or private metadata. Rendering filters must return valid content and avoid recursive calls to the same post helper.

pom_translate_should_translate_post_field( bool $enabled, int $post_id, string $field ) lets an integration own a complete field. Supported fields are post_title, post_content and post_excerpt. Return false for an exact post and field to skip string extraction and runtime reconstruction. Returning true does not enable a field disabled by the normal runtime content-type settings. Reparse an existing post to remove previously extracted field strings.

For HTML that is already localized, set data-pom-translate="skip" on its containing element. The parser, registered-string output replacement custom URL replacement and automatic internal-link localization skip that element and its descendants. The marker does not sanitize HTML: the integration remains responsible for safe output. This is useful for complete translated documents that should not be split into individual strings.