You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Edmund Horner <ch...@chrysophylax.cjb.net> on 2004/04/01 10:49:43 UTC
Re: Version numbers in MS Office documents
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Ralf.Bauer-Malz@etas.de wrote:
| Hello,
|
| has anybody already had the idea of writing the version number (or any
| other keywords) into MS Office documents by pre-commit scripts?
|
| I would much appreciate any hints (ideas, solutions?).
I think the main problems are:
1. You'll need a pre-commit program that understand MS Office formats.
2. You'll need to somehow modify the data in the transaction. svnlook
can't do that, but I suppose you could use the SVN bindings to
manipulate the transaction in the DB. Another method would be to build
a new transaction from the old one, commit it, and discard the old one
(somehow).
Other than that it sounds easy. Hope it goes well.
Edmund.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFAa/PHEbvImmpUq7gRArMLAKDvmL5XCAYVp0OBPhdapR1JnyD01QCg2Ytg
hDc6fbuO0xhtgFmyAb+KblI=
=n3Be
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Version numbers in MS Office documents
Posted by Edmund Horner <ch...@chrysophylax.cjb.net>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Max Bowsher wrote:
| Edmund Horner wrote:
|
|>-----BEGIN PGP SIGNED MESSAGE-----
|>Hash: SHA1
|>
|>Ralf.Bauer-Malz@etas.de wrote:
|>
|>>Hello,
|>>
|>>has anybody already had the idea of writing the version number (or any
|>>other keywords) into MS Office documents by pre-commit scripts?
|>>
|>>I would much appreciate any hints (ideas, solutions?).
|>
|>I think the main problems are:
|>
|>1. You'll need a pre-commit program that understand MS Office formats.
|>2. You'll need to somehow modify the data in the transaction. svnlook
|>can't do that, but I suppose you could use the SVN bindings to
|>manipulate the transaction in the DB. Another method would be to build
|>a new transaction from the old one, commit it, and discard the old one
|>(somehow).
|>
|>Other than that it sounds easy. Hope it goes well.
|
|
| You absolutely *cannot* modify the versioned content of a transaction
during
| pre-commit, becuase the committing client will not know about the changes,
| and will then have a weirdly broken working copy.
|
| You would need to introduce a new variant of successful commit that
says to
| the client "commit succeeded, but you may *not* assume that you now
have the
| committed revision of the nodes you sent".
Ah, you're absolutely right in both cases.
Sorry, Ralf, for making it sound so easy. :-)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFAbBg/EbvImmpUq7gRAhWjAKCur+t0zCNby1CG893gDE3F58YOFACguBzN
YZrGK7HI/vhQ0iJ+dsZHB0M=
=GPu0
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Version numbers in MS Office documents
Posted by Max Bowsher <ma...@ukf.net>.
Edmund Horner wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Ralf.Bauer-Malz@etas.de wrote:
>> Hello,
>>
>> has anybody already had the idea of writing the version number (or any
>> other keywords) into MS Office documents by pre-commit scripts?
>>
>> I would much appreciate any hints (ideas, solutions?).
>
> I think the main problems are:
>
> 1. You'll need a pre-commit program that understand MS Office formats.
> 2. You'll need to somehow modify the data in the transaction. svnlook
> can't do that, but I suppose you could use the SVN bindings to
> manipulate the transaction in the DB. Another method would be to build
> a new transaction from the old one, commit it, and discard the old one
> (somehow).
>
> Other than that it sounds easy. Hope it goes well.
You absolutely *cannot* modify the versioned content of a transaction during
pre-commit, becuase the committing client will not know about the changes,
and will then have a weirdly broken working copy.
You would need to introduce a new variant of successful commit that says to
the client "commit succeeded, but you may *not* assume that you now have the
committed revision of the nodes you sent".
Max.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org