返回提示词目录第 1314 页

审查开发文档的多语言翻译准备

检查文档结构中的翻译障碍,整理分级修复清单、禁译术语及首批翻译页面优先级。

完整提示词

<context>
Developer docs are harder to translate than ordinary prose because code, product names, UI labels and prose are interleaved in one source file. Translation projects for docs fail in predictable ways: sentences assembled from variables or reusable snippets that cannot be reordered in other languages; code identifiers, CLI flags and config keys translated by mistake; screenshots and diagrams with baked-in English text; examples with US-only dates, currencies, phone numbers or addresses; UI labels in the docs that do not match the translated product strings; and heading-based anchors that change per language and break links. This review is about structure and readiness, not line editing. Tooling: {{docs_tooling}}. Target languages and method: {{target_languages}}.
</context>

<task>
<docs_sample>
{{docs_sample}}
</docs_sample>

1. Scan the source for blockers and classify each finding:
   - built text: sentences assembled from variables, includes or components, or plurals handled in English only;
   - code in prose: identifiers, flags, keys, file paths or values not wrapped in code formatting, so translators or machine translation will change them;
   - UI references: product labels written in prose instead of referenced from the product's string catalog or marked as UI text;
   - media: images, diagrams and videos with embedded text, and alt text that is missing or says "image";
   - locale-bound examples: dates, numbers, currencies, units, names, addresses, phone numbers, and cultural references or idioms;
   - links and anchors: anchors generated from headings, hard-coded English URLs, links to English-only external pages;
   - markup hazards: inline HTML or JSX that splits a sentence, admonitions or tabs whose titles are not translatable strings, front matter fields that should or should not be translated.
2. For each finding give the location, why it breaks translation, the fix in the source, and severity: blocking (translation will produce wrong or broken pages), costly (extra work per language) or minor.
3. Build a do-not-translate list from the sample: product and feature names, API names, commands, config keys, error codes, and terms the team wants kept in English, each with a note.
4. Propose page priority for the first translation wave: pages most read by new users in the target markets (installation, quickstart, top tasks), then the rest; reference generated from code may need a different route (keep English, or translate descriptions only). Say what data would confirm the order.
5. Note process essentials: a source freeze or change-tracking approach so translations do not go stale, explicit anchor ids, a pseudo-translation build to catch hard-coded strings, and review by a technical speaker of each language.
</task>

<constraints>
- Base findings only on the sample; say how to search the full docs for the same pattern (a regex or a lint rule) rather than claiming it is everywhere.
- Do not rewrite whole pages; show before and after only for the lines you fix.
- Do not claim a docs tool or translation platform supports a feature unless it is well known; otherwise mark "(check your tool)".
- If no sample files are given, ask for them and stop.
</constraints>

<output_format>
## Summary
Three to five sentences: readiness, biggest blockers, rough effort.
## Blocking issues
Table: location, category, problem, fix.
## Fix list
Table for costly and minor issues: location, category, before, after.
## Do-not-translate list
Table: term, type (product, API, command, key, code), note.
## Page priority
Numbered list of pages or groups with the reason.
## Process notes
Bullets, each with one concrete action.
</output_format>

可替换内容

  • {{docs_tooling}}
  • {{target_languages}}
  • {{docs_sample}}

分类与标签

语言翻译、文档本地化、翻译准备、禁译术语、多语言文档

前往 AI 图片创作