word

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Chinese

<quality_workflow> For all professional deliverables, you MUST follow the "Render & Review" loop:

Edit: Use
```
python-docx
```
for structure/styling or the Document library for XML edits.

Render: Convert to PDF/PNG using

soffice

and

pdftoppm

soffice --headless --convert-to pdf document.docx

Inspect: Read the generated PNG images. You MUST look for clipped text, overlapping shapes, or misaligned margins.
Fix: Address defects and repeat the loop until the document is visually flawless. </quality_workflow>

<technical_workflows>

<quality_workflow> 对于所有专业交付成果，您必须遵循“渲染与审核”循环：

渲染：使用

soffice

和

pdftoppm

转换为PDF/PNG：

soffice --headless --convert-to pdf document.docx

<technical_workflows>

Python: You SHOULD use
```
python-docx
```
. Establish hierarchy with HeadingLevel styles.
JavaScript: You SHOULD use
```
docx-js
```
. Reference: See
```
references/docx-js.md
```
for syntax.
CRITICAL: You MUST NOT use
```
\n
```
for line breaks (use Paragraphs). You MUST NOT use Unicode bullets (use numbering config).
```
PageBreak
```
MUST be inside a Paragraph.

Python：您应使用
```
python-docx
```
。通过HeadingLevel样式建立文档层级。
JavaScript：您应使用
```
docx-js
```
。参考：查看
```
references/docx-js.md
```
获取语法说明。
关键注意事项：禁止使用
```
\n
```
换行（请使用段落）。禁止使用Unicode项目符号（请使用编号配置）。
```
PageBreak
```
必须放在段落内。

For legal or business review:

Initialize: Use
```
scripts/document.py
```
. Reference: Read
```
references/ooxml.md
```
for XML patterns.
Procedure: Unpack (
```
unpack.py
```
), edit XML using the Document Library, then Pack (
```
pack.py
```
).
Standard: You MUST only mark text that actually changes. Keep unchanged text outside
```
<w:del>
```
/
```
<w:ins>
```
.

针对法律或商业审核场景：

You SHOULD use Pandoc to convert to markdown while preserving structure:
- ```
pandoc --track-changes=all path-to-file.docx -o output.md
```
  </technical_workflows>

<quality_expectations>

Client-Ready: You MUST NOT use Unicode dashes (use ASCII hyphens). No internal AI tokens.
Element Ordering: In
```
<w:pPr>
```
, elements MUST follow schema order: Style -> Numbering -> Spacing -> Indent -> Alignment.
Visual Fidelity: Charts and tables MUST be sharp and legible in rendered previews. </quality_expectations>

</word_document_professional_suite> </instructions>

您应使用Pandoc将文档转换为markdown并保留结构：
- ```
pandoc --track-changes=all path-to-file.docx -o output.md
```
  </technical_workflows>

<quality_expectations>

</word_document_professional_suite> </instructions>