# 독일어 번역에 번역 요소가 포함되어 있습니다
**URL:** https://meta.discourse.org/t/german-translations-contain-translation-elements/407009
**Category:** Bug
**Tags:** ai, dynaloc, content-localization
**Created:** [7월 7, 2026, 7:06오후 UTC](https://meta.discourse.org/t/german-translations-contain-translation-elements/407009 "2026-07-07T19:06:57Z")
**Posts on this page:** 1
**Showing post:** 2
### Author:  [@Falco](https://meta.discourse.org/u/Falco)
#### Post date: [7월 7, 2026, 7:10오후 UTC](https://meta.discourse.org/t/german-translations-contain-translation-elements/407009/2 "2026-07-07T19:10:04Z")
번역용 프롬프트에 몇 가지 논리적 모순이 있는 것 같습니다. 여기에 수정안을 제안했습니다.
>
>
> Previously, the translation agents (\`PostRawTranslator\`, \`TopicTitleTranslator\`,… and \`ShortTextTranslator\`) embedded their few-shot examples directly in the system prompt as \`Input:\`/\`Output:\` text, where the example inputs were JSON but the outputs were bare text — contradicting the \`response\_format\` that requires a \`{"output": "..."}\` object. This conflicting guidance caused some models to echo the input wrapper into published translations, e.g. German localizations starting with \`{"content":"...\` as reported in https://meta.discourse.org/t/german-translations-contain-translation-elements/407009.
>
> This change moves the examples to the \`examples\` hook — which pre-seeds them as real user/model turns in the conversation, like our other agents (\`Proofreader\`, \`LocaleDetector\`, \`SmartDates\`) — with each model turn serialized as \`{"output": "..."}\` so the examples demonstrate the exact structured output the agent must produce. It also drops the now-unnecessary instruction claiming a bare ASCII \`"\` would truncate the response (the structured output layer handles escaping), and removes a stray trailing quote that had leaked into the Japanese example.
---
_[View the full topic](https://meta.discourse.org/t/german-translations-contain-translation-elements/407009)._