Comments on: Working with iWork and Subversion http://onemanswalk.com/work/2007/11/04/working-with-iwork-and-subversion/ jeremy lightsmith on agile, ruby, and consulting Thu, 29 Jul 2010 06:35:47 +0000 http://wordpress.org/?v=2.9.1 hourly 1 By: Wes Maldonado http://onemanswalk.com/work/2007/11/04/working-with-iwork-and-subversion/comment-page-1/#comment-39 Wes Maldonado Sun, 04 Nov 2007 22:56:00 +0000 #comment-39 I knew something was wrong when I saw that check in... Elisabeth Hendrickson wrote about [the same keynote problem](http://www.testobsessed.com/2007/10/16/oh-the-irony/) a while back... as did [Brian Marik](http://www.exampler.com/blog/2007/10/16/im-looking-at-you-keynote/) I knew something was wrong when I saw that check in… Elisabeth Hendrickson wrote about [the same keynote problem](http://www.testobsessed.com/2007/10/16/oh-the-irony/) a while back… as did [Brian Marik](http://www.exampler.com/blog/2007/10/16/im-looking-at-you-keynote/)

]]> By: Trevor http://onemanswalk.com/work/2007/11/04/working-with-iwork-and-subversion/comment-page-1/#comment-40 Trevor Sun, 04 Nov 2007 22:56:00 +0000 #comment-40 Regarding #1, I believe there's a method to iWork's madness. Its Microsoft Office importers/exports are far from perfect, so they really can't handle round-trip saves. If you were to open, say, a Word file, make a few small edits, and then save it back to Word, the results might not be what you expect. You'll get progressive defects the more you do this, kind of like what happens when you make a copy of a copy of a copy of an analog recording. Forcing you to do an explicit export instead of a simple save is a reminder that your file is about to embark on a one-way trip. By the way: "stores it’s files" --> "stores its files" Regarding #1, I believe there’s a method to iWork’s madness. Its Microsoft Office importers/exports are far from perfect, so they really can’t handle round-trip saves. If you were to open, say, a Word file, make a few small edits, and then save it back to Word, the results might not be what you expect. You’ll get progressive defects the more you do this, kind of like what happens when you make a copy of a copy of a copy of an analog recording. Forcing you to do an explicit export instead of a simple save is a reminder that your file is about to embark on a one-way trip.

By the way: “stores it’s files” –> “stores its files”

]]> By: Anders http://onemanswalk.com/work/2007/11/04/working-with-iwork-and-subversion/comment-page-1/#comment-41 Anders Sun, 04 Nov 2007 22:56:00 +0000 #comment-41 Thanks for your very nice Ruby script. This bug in iWork has been annoying me for ages. Thanks again! /Anders, Denmark Thanks for your very nice Ruby script. This bug in iWork has been annoying me for ages. Thanks again!

/Anders, Denmark

]]> By: jon http://onemanswalk.com/work/2007/11/04/working-with-iwork-and-subversion/comment-page-1/#comment-42 jon Sun, 04 Nov 2007 22:56:00 +0000 #comment-42 Thanks much! I wish apple would get it together as well. Just modify the existing bundle and only replace what changes... jc Thanks much! I wish apple would get it together as well. Just modify the existing bundle and only replace what changes…

jc

]]>