独立开发与工具 Stack Exchange · 2024-03-01

用 Git 管理技术文档？diff 对 .docx 基本无效

Using Git for technical docs? Diff is useless for .docx

30 秒速览

谁在提Stack Exchange · 2024-03-01 · 1 赞 · 2 评
想要什么用 Git 管理技术文档？diff 对 .docx 基本无效
能做成什么Word↔Markdown 智能转换 + 语义 diff 渲染的 CI 机器人：在 PR 里直接显示文档改动预览。

原帖原话

“The team wants Git for product docs. Markdown is fine, but contracts/specs are Word files — binary diffs and merges are terrible.”

“团队想用 Git 管理产品文档。Markdown 没问题，但合同/规格书是 Word 格式，二进制 diff 和 merge 体验极差。”
— Stack Exchange · 2024-03-01 · softwarerecs.stackexchange.com/questions/89985/is-it…

需求背景与痛点

痛在哪

企业文档工程化是真实趋势，但 Word 生态和 Git 之间缺一层可用的转换/预览/合并工具。

可以做成什么

能做成什么

Word↔Markdown 智能转换 + 语义 diff 渲染的 CI 机器人：在 PR 里直接显示文档改动预览。

怎么验证它

读完原帖的评论区，把重复出现的具体场景记下来——重复次数就是需求的密度。
搜索「文档管理 / Git」相关的现有工具，确认它们只覆盖了哪一环。
用一句话落地页，投回 Stack Exchange 或同类社群，看有没有人主动问价格。

已有方案与差异

Pandoc（命令行，无 diff 渲染）；SharePoint（另一套生态）

社区原声 · 热门评论

热门评论由机器翻译为中文，点击原帖核对原意。

You can use GIT for any files. I store code, images, notes, documentation, help files and even database schema, all in one place. Basically everything except the executable and the database. So a version branch has all the related information. There is absolutely no issue storing binary files in GIT, apart from more storage (as you have noted).

— Rohit Gupta · ▲ 2

You can do what you are describing, it will just use more space. Below I give an alterative approach that is closer to how Git is intended to be used that allows for in-document change tracking and significantly smaller file sizes. Ideally your PDFs would be generated from a text-based input such as LaTeX and then you would have the source in one place and be able to see differences between versions as intended with Git. While you can, you should not use Git for generated files such as PDFs and instead these should be uploaded as releases on GitHub/GitLab. You should also track the script used

— Henry Ginn · ▲ 1

打开原帖核对

同一痛点的其他讨论

开发者工具与基础设施 (7)