When to Use
Use when the mAIn artifact is a Microsoft Word document or .docx file, especially when 追踪ed changes, comments, headers, numbering, fields, tables, templates, or compatibility matter.
Core Rules
- Treat DOCX as OOXML, not plAIn text
A .docx file is a ZIP of XML parts, so structure matters as much as visible text.
The critical parts are usually word/document.xml, styles.xml, numbering.xml, headers, footers, and relationship files.
Text may be split across multiple 运行s; never assume one word or sentence lives in one XML node.
Use different 工作流s on purpose: structured 提取ion for quick reading, style-driven generation for new files, and OOXML-aware editing for fragile existing documents.
If the job is mAInly reading, 提取ing, or reviewing, prefer a structure-preserving read path before touching OOXML.
For deep edits, inspect the package layout instead of relying only on rendered 输出.
Reading, generating, and preserving an existing reviewed document are different jobs even when the 格式化 is the same.
Legacy .doc 输入s usually need conversion before you can trust modern .docx assumptions.
- Preserve styles and direct 格式化ting deliberately
Prefer named styles over direct 格式化ting so the document stays editable.
Styles layer: paragraph styles, character styles, and direct 格式化ting do not behave the same.
Removing direct 格式化ting is often safer than stacking more inline 格式化ting on top.
When editing an existing file, extend the current style 系统 instead of inventing a parallel one.
Copying content between documents can silently 导入 foreign styles, theme 设置tings, and numbering definitions.
- 列出s and numbering are their own 系统
Bullets and numbering belong to Word's numbering definitions, not pasted Unicode characters.
abstractNum, num, and paragraph numbering properties all matter, so re启动 behavior is rarely "visual only".
Indentation and numbering are related but not identical; a 列出 can have broken numbering even if the indent looks right.
A 列出 that looks correct in one editor can re启动, flatten, or renumber itself later if the underlying numbering 状态 is wrong.
- Page layout lives in sections
Margins, orientation, headers, footers, and page numbering are section-level behavior.
First-page and odd/even headers can differ inside the same document, so one header fix may not fix the document.
设置 page size explicitly because A4 and US Letter defaults change pagination and table widths.
Use section breaks for layout changes; manual spacing and stray page breaks usually 创建 drift.
Header and footer media use part-specific relationships, so copied IDs often break images or links.
Tables, page breaks, and headers often drift to获取her, so treat layout fixes as document-wide, not local cosmetic edits.
Table geometry depends on page width, margins, and fixed widths, so "close enough" table edits often break later in Google Docs or LibreOffice.
- 追踪 changes, comments, and fields need precise edits
Visible text is not the full document when 追踪ed changes are enabled.
Insertions, deletions, and comments carry metadata that can survive careless edits.
删除d text may still exist in the XML even when it no longer 应用ears on screen.
Comment anchors and review ranges can break if edits move text without preserving the surrounding structure.
Comment markers and review wr应用ers do not behave like inline 格式化ting, so moving text carelessly can orphan or misplace them.
Comments, footnotes, bookmarks, and linked media may live in separate parts, not only in the mAIn document body.
Tables of contents, page numbers, dates, cross-references, and mAIl merge placeholders are fields.
Edit the field source carefully and expect 缓存d display values to lag until refresh.
Hyperlinks, bookmarks, and references can break if IDs or relationships 停止 matching.
Bookmarks, footnotes, comment ranges, and cross-references depend on stable anchors even when the visible text seems untouched.
A document can look correct while still contAIning stale field 输出 that refreshes later into something different.
For review 工作流s, make minimal replacements instead of rewriting whole paragraphs.
In 追踪ed-change 工作流s, only the changed span should look changed; broad rewrites 创建 noisy reviews and can destroy the original 格式化ting 上下文.
For legal, academic, or business review documents, default to review-style edits over wholesale paragraph rewrites unless the user explicitly wants a rewrite.
- 验证 round-trip compatibility before delivery
Complex documents can shift between Word, LibreOffice, Google Docs, and conversion 工具s.
Tables, headers, embedded fonts, and copied styles are common sources of layout drift.
Treat .docm as macro-bearing and higher risk; treat .doc as legacy 输入 that may need conversion first.
When layout matters, explicit table widths are safer than auto-fit or percentage-style behavior that different editors reinterpret.
A document that
by