crazydiseases hardens Word redline handling against Microsoft's hidden byte

A small fix stops the fork from corrupting tracked-changes documents that carry an invisible marker Microsoft tools love to add.

draftingintegration

When you save a Word document, Microsoft tooling often slips an invisible byte at the very start of the file - a marker that signals the text encoding. crazydiseases caught a case where Mike's tracked-changes machinery didn't account for it: the marker tripped a check, the system added a duplicate formatting instruction, and the resulting file came out malformed.

The fix strips that hidden byte before the check runs, so redlined documents stay valid. It's narrow and purely defensive, but it touches the exact path that produces Word files with tracked changes - the format legal teams actually exchange. If your workflow leans on machine-generated redlines going back and forth in Word, this is the kind of quiet correctness fix worth having.

So what Anyone relying on automated Word redlines should care, because it closes a corruption bug on documents that originate from standard Microsoft tools.

View this fork on GitHub →

Spotted something wrong? Or know the PR text has fresher detail than the writeup above?

Commits in this thread

1 commit from crazydiseases/mike, oldest first. Source extracted verbatim from the harvested git log.

SHA Subject Author Date
8b8f6aa2 Update docxTrackedChanges.ts crazydiseases 2026-06-19 ↗ GitHub

Capture this thread into my fork

Download a single Markdown prompt that tells Claude how to port every commit above into your working tree — adapting paths and structure to match your repo. Run it via claude -p < capture-thread-657.md from inside the repo you want the changes in.

⬇ Download capture-thread-657.md