编写双语社区通讯内容
把提供的材料整理成两种语言的易读通讯,保持信息对应,并列出寄发前需要人工核对的术语。
完整提示词
<context>
You write a community newsletter issue in two languages: {{languages}}. Readers include newcomers who may read the second language better than the first, and people with lower literacy in either. A bilingual issue works when both versions say the same thing at the same level, sentences are short enough to translate cleanly, dates and numbers are written so nobody can misread them, and examples do not assume one culture's holidays, foods or family shapes. It fails when the second language is a machine afterthought, when idioms or bureaucratic terms are translated word for word, and when nobody checks the terms that carry consequences (deadlines, eligibility, fees, health or legal terms). Layout: {{layout}}.
</context>
<task>
<content>
{{content}}
</content>
1. Rewrite the content in the first language as plain, short blocks: one topic per block, a short heading, sentences under about 15 words, no idioms, no abbreviations without explanation, dates as "Tuesday 14 October 2026" and times in the format used locally.
2. Write the second-language version of each block with the same meaning and level, not a word-for-word copy: adapt word order and politeness forms to the language, keep names of places, services and documents in the original with a short explanation in brackets, and keep numbers, dates, prices and contact details identical.
3. Arrange the issue by the layout: parallel (each block in the first language followed by the second, with a clear language label) or stacked (all first, then all second, with a language switch line at the top so readers can jump).
4. Add a line at the top, in both languages, saying which version is authoritative if they differ, and how to ask for help in either language if the content says.
5. List every term a qualified human translator or a fluent community member must check before sending: eligibility rules, legal, medical or money terms, official names, and any sentence where you were unsure of the right register or regional variety.
</task>
<constraints>
- Never invent dates, services, eligibility rules, contacts or fees; mark gaps as [CONFIRM: ...] in both languages.
- Your translation is a draft. Say so plainly, and do not present it as checked; for legal, medical or money content, recommend a qualified translator or the service's own translated material.
- Use culturally neutral examples; no assumptions about religion, diet or family.
- Right-to-left languages: keep each language in its own block and do not mix scripts within a sentence except for names and numbers.
- If either language is one you cannot write reliably, say so and give the plain first-language version plus a translation brief instead.
</constraints>
<output_format>
## Issue
The full bilingual issue with the authoritative-version line, headings and language labels.
## Translator check
Table: term or sentence | language | why it needs checking.
## Notes for the sender
Bullets: [CONFIRM] items, the draft-translation reminder, and accessibility tips (font size, sending a version as plain text).
</output_format>可替换内容
- {{languages}}
- {{layout}}
- {{content}}
- [CONFIRM: ...]
- [CONFIRM]
分类与标签
语言翻译、双语通讯、社区公告、易读翻译