On 14/06/2014 04:51 PM, andrel wrote:
> For the source control part...
> Both .docx and .odt are in fact zip containers that contain the images
> and the content in different files. In theory you could extract the
> content part, put that under revision control.

Yeah, but that probably won't work well in practice.

For example, we use a system called SpecFlow where you write integration 
tests in psuedo-English, and an external DLL transforms that into C# 
code. Both the source and the generated C# code are in source control. 
But the trouble is, if you insert or remove a single line in the 
SpecFlow file, the *entire* C# file changes. (Every line of the 
generated file is annotated with the corresponding line number in the 
SpecFlow file.)

I rather suspect that when you save an ODF file, the editor rebuilds the 
entire file and it won't look anything like what it did before. (I 
haven't tried, but I suspect that's what'll happen.) The other problem, 
of course, is that it's hard to make really polished ODF files in the 
first place. ;-)

> Alternatively, many programs nowadays support
> version control. Did you check if InDesign does?

As I say, nobody here seems to know how to work InDesign. It wouldn't 
surprise me if our current workflow can be significantly improved just 
by changing how the document it set up...

Post a reply to this message