> On Mon, Sep 29, 2003 at 10:09:11AM -0500, Ben Collins-Sussman wrote:
> > Anders Engstr=F6m <firstname.lastname@example.org> writes:
> > > Any comments on this?
> > The subversion repository only stores "contracted" keywords, like
> > $Id$. All keyword expansion is done by the client, in the working
> > copy.
> > So I don't think you'd need any magic scripts to modify word
> > documents, other than inserting an $Id$ keyword (in the correct
> > place!) the very first time the Word doc is committed to the
> > repository. After that, the svn client will do everything for you
> > automatically.
> Interesting... In CVS word files are handled as binary files (and
> keyword substitution is disabled - that's why we have the commitinfo
Keyword substitution is disabled in CVS *only* if you set the -kb flags
on the file, which can either be done through your .cvswrappers file or
manually. If, however, you forget to do this, CVS will happily munge
your binary files, doing both keyword substitution and EOL translation.
In Subversion the default is to do neither.
> I know subversion is supposed to handle merging/keyword-substitution
> in binary files as well
Merging of binary files? Not that I recall... perhaps you're confusing
this with the fact that Subversion efficiently stores binary files on
the server (Unlike CVS which stores a fulltext copy of each revision of
a binary file)?
> and if subversion can handle keywords in MS
> Word-files our issues would disappear (a Word template with $Author$,
> $Id$ etc. would be all that was needed).
Well, as CMike pointed out, this is really a limitation of MS Word's
file format--if we changed the length of a string in a Word file, it
would trash the file if Word relies on counted offsets.
> Anyone with exprerience of svn/cvs keywords in binary files?
Not I. :)
Brian W. Fitzpatrick <fitz_at_red-bean.com> http://www.red-bean.com/fitz/
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Mon Sep 29 17:36:46 2003