Questions Regarding PTC Automated Translation Workflow

This is the technical support forum for WPML - the multilingual WordPress plugin.

Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.

Sun	Mon	Tue	Wed	Thu	Fri	Sat
9:00 – 13:00	9:00 – 13:00	9:00 – 13:00	9:00 – 13:00	9:00 – 13:00	-	-
14:00 – 18:00	14:00 – 18:00	14:00 – 18:00	14:00 – 18:00	14:00 – 18:00	-	-

Supporter timezone: Asia/Yerevan (GMT+04:00)

This topic contains 1 reply, has 0 voices.

Last updated by Christopher Amirian 3 months, 1 week ago.

Assisted by: Christopher Amirian.

Author	Posts
May 8, 2026 at 2:45 pm #18023329
davidH-81	Hi team, We recently started testing the PTC automated translation workflow in WPML and discovered a few issues or limitations we would appreciate some support / guidance on. Our first challenge is related to custom post types and dynamic backend fields. For many of our content formats, the backend contains a large number of settings, checkboxes, and dynamic fields that control the front-end appearance (layout variations, labels, colors, visibility of sections, etc.). Without configuring these settings, the page is often not properly previewable on the front-end (I'm attaching a couple of screenshots of our blog template backend as an example of how these settings look like). This currently creates friction in the WPML workflow. After sending a page for translation, WPML correctly moves us into the translation/review process. However, before we can properly review the translated version, we first need to: - go back to the original page, - switch to the translated draft, - manually configure all required settings again, - save the page, - and only then return to WPML to review the translation properly. As you can imagine, this makes the workflow quite cumbersome for our translators and editors. Our question here is: Is there any way for the translated draft to automatically inherit/copy the backend settings from the original page, so we can proceed directly with the review workflow without manually recreating the setup each time? --- Our second question is related to tone of voice and translation quality. While the translations are generally accurate in terms of grammar, we notice that the tone often becomes more dry and factual compared to the original content, losing some of the intended phrasing and communication style. Are there any possibilities to: feed the AI with some tone-of-voice examples or writing samples, further customize the translation behavior, or use any add-ons/integrations that would help the output better reflect our communication style? If it would be easier to better understand the setup and workflow on our side, we would also be happy to schedule a short call on Monday or Tuesday next week and walk you through our backend and current process. Thanks a lot in advance! We really appreciate any recommendations or best practices you could share!
May 10, 2026 at 9:36 am #18024946
Christopher Amirian WPML Supporter since 07/2020 Languages: English (English ) Timezone: Asia/Yerevan (GMT+04:00)	Hi, Welcome to WPML support. Let me address both concerns. 1. Custom post type backend settings not inheriting on translation drafts What you're describing is exactly what WPML's Custom Fields Translation Preferences are designed to solve. Each custom field (whether from ACF, Meta Box, JetEngine, Toolset, or a custom register_post_meta registration) can be set to one of four behaviours: Translate — for text-bearing fields (labels, headings, descriptions). The field value will appear in the translation editor for the translator/AI to translate. Copy — for fields where the same value should always appear in every language (layout selectors, checkboxes, visibility toggles, color picks, image IDs, numeric values). The original value is mirrored to all translations and kept in sync — if you change it on the original, the translation updates automatically. Copy once — copies once on the first translation, then translations can diverge. Useful for fields where you want a default copy but language-specific overrides. Don't translate — WPML ignores the field. Default for unconfigured fields. For your case (layout variations, section visibility toggles, colors, etc.), almost all of these settings should be set to Copy. That way, the moment a translation draft is created, it already has all the layout settings of the original — no manual reconfiguration step before review. And any later change you make to the layout on the original page automatically propagates to all language versions. Go to WPML → Settings → Custom Fields Translation — lists every detected custom field on your site with a translation-preference selector. For more information: https://wpml.org/documentation/getting-started-guide/translating-custom-fields/ 2. Tone of voice / matching your communication style Go to WPML → Settings → AI Translation section and fill in the context fields about your site's purpose, audience, and brand voice. This is not a small form to fly through — it has the largest single influence on the tone PTC produces. Be specific about: - Industry/niche - Target audience (B2B / B2C, formality level, demographics) - Brand voice (e.g., "warm and conversational, avoids corporate jargon, uses active voice and direct address") - Formality preference (especially important for languages with formal/informal distinctions like German Sie/du) For more information: https://wpml.org/changelog/2025/08/wpml-4-8-human-quality-ai-translations/ hidden link Also, WPML has a Glossary feature that might help when it comes to special phrases or words. For more information: https://wpml.org/documentation/translating-your-contents/advanced-translation-editor/how-to-create-and-manage-glossary-entries/ Thanks.

The topic ‘[Closed] Questions Regarding PTC Automated Translation Workflow’ is closed to new replies.