獨立開發與工具 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)