Hi Joseph...? Thanks for setting this straight.? I guess that would mean that saving in binary would be better than trying MIF as a text format for SVN!? Wow, imagine that.?
________________________________ From: Joseph Lorenzini <jaloren at gmail.com> To: despopoulos_chriss at yahoo.com Cc: FrameMaker Forum <framers at lists.frameusers.com> Sent: Monday, September 24, 2012 9:59 AM Subject: Re: Document Revision Control Hi Chris, This issue you raised about binary files and SVN used to be true but is somewhat inaccurate now. I stayed away from SVN for a really long time because of this very issue. I thought it was ridiculous that every time I would make a commit, SVN would commit an entirely new version of the file.? However, a couple years ago, the IT admin, who manages the SVN repos for my company, explained that later versions of SVN can in fact commit just the differences between two versions of the same binary file. I was able to confirm this with some testing of my own. The size of my doc repo would be exponentially larger if every commit was the entire FrameMaker file instead of the difference. Now with that said, the following is still true: 1. committing large binary files is considered bad form and frowned upon from an engineering point of view. That's because SVN doesn't manage binaries nearly as well as it can handle text files. 2. The key thing that SVN still cannot do is actually perform SVN blame or diff two versions of the file for you. It can only commit the difference, it can't identify and compare the difference between version 1 and version 2 for you.
