It's almost certainly "accidental" and a relic of some indexing or something that Sharepoint is doing to the documents. I'll bet it recognizes XML-ish content (as the article notes, images and plain text are ignored), tosses it in a validator or something similar that "corrects" the file, and saves that file internally. That's not too unusual in the CMS world. The bad part is that the internal version has found its way back out; hopefully in turning SharePoint into "cloud storage" they screwed up and sent the wrong thing. Otherwise, that's rather a mis-feature of SharePoint. If there's anyone here who actually knows it (I only generally do, being on the OSS side of the CMS world) I'd be interested to know.
So I'm ascribing this to incompetence and/or bad judgement rather than malice. But either way, still unacceptable.
Sure, but as a cloud sync product it's a "you had one job" situation. Not so much incompetence as a fundamental failure to achieve that basic requirement.
So I'm ascribing this to incompetence and/or bad judgement rather than malice. But either way, still unacceptable.