# 德语翻译包含翻译元素

**URL:** <https://meta.discourse.org/t/german-translations-contain-translation-elements/407009>\
**Category:** Bug\
**Tags:** ai, dynaloc, content-localization\
**Created:** [2026年七月7日 19:06 UTC](https://meta.discourse.org/t/german-translations-contain-translation-elements/407009 "2026-07-07T19:06:57Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![putty](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/putty/32/370902_2.png) [@putty](https://meta.discourse.org/u/putty)\
**Post date:** [2026年七月7日 19:06 UTC](https://meta.discourse.org/t/german-translations-contain-translation-elements/407009/1 "2026-07-07T19:06:57Z")

</div>

[Similar to my bug report here](https://meta.discourse.org/t/ai-commentary-on-german-translations/399805), I’ve noticed on several occasions that German translations keep some of the coding around the translation process (sorry, don’t actually know what to call this). [See here for an example in our community](https://community.netwrix.com/t/support-for-passkeys/13564/7?u=derek.putnam).

German:

> Wir sehen bei unseren Kunden eine zunehmende Einführung von Passkeys als Standard für die Benutzerauthentifizierung. Die Unterstützung zur Speicherung und Verwaltung von Passkeys wird daher immer mehr zu einer grundlegenden Anforderung an Enterprise Password Manager.

Translates to:

> {“content”:“We’re seeing an increasing rollout of passkeys as the standard for user authentication among our customers. As a result, support for storing and managing passkeys is becoming an ever more fundamental requirement for an enterprise password manager.”}

Unrelated to this somewhat, but it’s impossible to edit the translations when the first post uses a form template:

---

<div class="post-metadata">

**Author:** ![Falco](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/falco/32/179432_2.png) [@Falco](https://meta.discourse.org/u/Falco)\
**Post date:** [2026年七月7日 19:10 UTC](https://meta.discourse.org/t/german-translations-contain-translation-elements/407009/2 "2026-07-07T19:10:04Z")

</div>

看起来我们的翻译提示词中存在一些逻辑矛盾，在此提出修复方案

> <https://github.com/discourse/discourse/pull/41526>
>
> 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.

---

<div class="post-metadata">

**Author:** ![putty](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/putty/32/370902_2.png) [@putty](https://meta.discourse.org/u/putty)\
**Post date:** [2026年七月7日 20:25 UTC](https://meta.discourse.org/t/german-translations-contain-translation-elements/407009/3 "2026-07-07T20:25:51Z")

</div>

重新贴出您之前的帖子，因为它可能与此相关：

> [@Falco](#):
>
> 您是否自定义了翻译代理，还是使用了我们提供的默认代理？

我们使用的是默认代理的副本，并针对产品名称对提示词进行了细微调整。

 ![CleanShot 2026-07-07 at 16.25.13](https://global.discourse-cdn.com/meta/original/4X/c/5/e/c5e783a80bc0f4a0f3a9074dfcd6b8363c8e764d.png)

考虑到这一点，您的修复方案是否仍能处理此问题，还是我需要更新我们代理的提示词？

---

<div class="post-metadata">

**Author:** ![Falco](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/falco/32/179432_2.png) [@Falco](https://meta.discourse.org/u/Falco)\
**Post date:** [2026年七月7日 20:29 UTC](https://meta.discourse.org/t/german-translations-contain-translation-elements/407009/4 "2026-07-07T20:29:59Z")

</div>

> [@putty](#):
>
> 我们使用的是默认代理的副本，并对提示词进行了微调以处理产品名称。

`Netwrix Post Translator` 代理的 JSON 响应格式部分是否已填写？

它应该看起来像这样

 ![image](https://global.discourse-cdn.com/meta/original/4X/0/e/1/0e16cb801eac06fab0d3c71abf226786a6c701dc.png)

> [@putty](#):
>
> 考虑到这一点，您的修复方案是否仍能处理这个问题，还是我需要更新我们代理的提示词？

您还需要更新您的副本以处理这些更新。好消息是，您甚至无需等待其合并，可以立即进行更新。

---

<div class="post-metadata">

**Author:** ![putty](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/putty/32/370902_2.png) [@putty](https://meta.discourse.org/u/putty)\
**Post date:** [2026年七月8日 14:17 UTC](https://meta.discourse.org/t/german-translations-contain-translation-elements/407009/5 "2026-07-08T14:17:44Z")

</div>

> [@Falco](#):
>
> `Netwrix Post Translator` 代理的 JSON 响应格式部分是否已填写？

答对了！原来没有填写。感谢你的修复，Falco！

---

<div class="post-metadata">

**Author:** ![Falco](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/falco/32/179432_2.png) [@Falco](https://meta.discourse.org/u/Falco)\
**Post date:** [2026年七月20日 11:00 UTC](https://meta.discourse.org/t/german-translations-contain-translation-elements/407009/7 "2026-07-20T11:00:41Z")

</div>

此主题在11天后自动关闭。不再允许新的回复。