Re: Content Management (was Anyone used Tortoise CVS with Frame Files)

2006-03-16 Thread Laura Lemay
On 3/15/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: As for MIF, a search of the archives might result in one members analysis of the bloat in file size caused by MIF and at what point saving diffs of MIF files is advantageous over saving whole binary versions. My experience with MIF is that

Content Management (was Anyone used Tortoise CVS with Frame Files)

2006-03-16 Thread Laura Lemay
On 3/15/06, eric.dunn at ca.transport.bombardier.com wrote: > As for MIF, a search of the archives might result in one members analysis > of the bloat in file size caused by MIF and at what point saving diffs of > MIF files is advantageous over saving whole binary versions. My experience with

Content Management (was Anyone used Tortoise CVS with Frame Files)

2006-03-16 Thread eric.d...@ca.transport.bombardier.com
Laura Lemay wrote on 03/16/2006 11:07:06 AM: > My experience with MIF is that for the purposes of source code control > it is the worst of both ascii and binary. MIF files may be ASCII but > they are really huge, and a significant part of the file is different > between saves in FM even if you

Content Management (was Anyone used Tortoise CVS with Frame Files)

2006-03-15 Thread Lynne A. Price
Don, I don't have the summary you requested, but if your XML documents round-trip, yes, definitely use XML in your versioning system. Just make sure to keep track of the version of all application files (DTD, template, r/w rules, application definition file, and of FrameMaker itself) used