4 ms·
OOXML is text based now. So Office 2007 should be text capable. Sharepoint is generally horrible with that I agree, but I think it uses the default MS word mech
by _pi 17y ago
OOXML is text based now. So Office 2007 should be text capable. Sharepoint is generally horrible with that I agree, but I think it uses the default MS word mechanism to do that which stores changes with the file at the end.... kind-of a bad idea.
Also fun fact: Sharepoint agreeably sucks more than any other MS product but it's not actually written by MS, but a large part of it is written/owned/supported by Akamai Technologies
- jmillikin 17y agoOOXML is typically stored as a compressed ZIP archive. Even when its decompressed to its constituent XML files, modifications are performed without much regard to how a diff will look. This applies to auto-generated XML in general -- ODT is not immune. LaTeX and reStructuredText are the only formats I know of which are suitable for professional publication and can be usefully diffed.
- _pi 17y agoThat's very interesting. Why is auto-generated XML hard to diff?
- superchink 17y agoThat's because XML does not guarantee order of elements.
- jamesbritt 17y ago"That's because XML does not guarantee order of elements." It better, or else it's broken. In XML, element order matters. Attribute order does not.
- atourino 17y agoConsider an XML file consisting of one long line of text. A diff would not be very useful in that case.
- michaelneale 17y agoI guess an XML aware diff could work though? certainly not at all line based...
- jamesbritt 17y agoIf it did node-based diffs.
- _pi 17y agoMost diffs do that. The Diff that ships with gvim on Windows has this option on by default and I couldn't find where to turn it off because it was severely screwing up what I was diffing.
- pseale 17y agoI'd be interested to hear where you get the Akamai Technologies-SharePoint link, I've only heard that SharePoint is wholly written by Microsoft.
- _pi 17y agoVery weird support call. I finally said listen I think it's a problem with Sharepoint, and they forwarded me to Akamai, however they answered the phone as MS, but the CallerID showed Akamai Technologies. If you've ever dealed with MS Business Support they have sections for every single product and some products are segmented by parts.
- pseale 17y agoOh. MS's SharePoint premier support is definitely staffed with contractors; the two times I called, I talked to non-employees. I wouldn't draw any conclusions about the development staff from that though.
- _pi 17y agoAkamai's services are almost too tightly integrate-able with sharepoint. Not only that I wouldn't call the support premier ;-)