News for hackers. Stuff that matters.

A comment on Write plain text files. Parent comment

Re:Write plain text files by loudmax on Tuesday March 01, 2022 @08:19PM (#30522443)
"Report Final Final draft v3.docx" is in a proprietary format format controlled by a single company. The spec may be open in some sense, but it's far from a level playing field.
[ Parent | on HN ]
Re:Write plain text files by sgjohnson on Wednesday March 02, 2022 @01:51AM (#30524517)
> is in a proprietary format format controlled by a single company.

It's not proprietary by definition. A nightmare to implement? Yes.

But definitely not proprietary.

[ Parent | on HN ]
Re:Write plain text files by _dain_ on Wednesday March 02, 2022 @07:50AM (#30526753)
It doesn't follow the published open spec so it is de facto proprietary.
[ Parent | on HN ]
Re:Write plain text files by yjftsjthsd-h on Wednesday March 02, 2022 @02:06AM (#30524600)
Right, but if that company released a diff tool for docx (or someone reverse engineered one), git would work with it. I don't expect that to happen, I'm just saying git isn't the limiting factor.
[ Parent | on HN ]
Re:Write plain text files by sgjohnson on Wednesday March 02, 2022 @03:49AM (#30525259)
Pre-commit hook to convert to plaintext or markdown[0].

And there you go, a human readable diff.

[0]https://github.com/benbalter/word-to-markdown

[ Parent | on HN ]