So I edited that back to <a></a> (easier to put info back in later), re-compared, and it was 'gone' again...
Then I remembered the autodetection, and indeed, switching back to to text it seems that my edits were indeed there (and probably weren't wrong originally), this was just caused by the interpretation as xml.
Some observations:
- It's a good idea! diffing on the standardized view will eliminate whitespace and other unimportant changes, like indeed the equivalent <a></a> and <a/>
- Editing on it seems to work well: I edited the 'interpreted' line and saved, and it came out ok. I'm now wondering however if other 'interpreted' lines would be saved as they were displayed ('interpreted') or as they were originally?
- I couldn't really see the fact that the document was shown after interpretation (and the resulting associated 'pretty printing') as xml, except from going to the menu. This is of course 'obvious' for a format like word or pdf where you'll see garbage if it's not interpreted, a little less so for xml since the difference between uninterpreted and interpreted may be very small.
So that results in one request: something to show what format interpretation(s?) compareIt has done. I was thinking about a balloon message on startup? Or something before or after the path that is displayed above each file? (That is less easy to see, but less intrusive.) Or the second thing always, and an option if you want the balloon? (I can imagine the balloon to be easy for people like me who normally diff code and are surprised by the interpretation of file formats like in my case here (even though I really like it!), but always clicking it away would be problematic for people who diff xml all day long
