> Well diff -a somewhat informative, although very messy. I can clean
> the diff of two zip -0 files as follows:

No one will actually use zip -0. When compression is used, it is used
to reduce file sizes.

> $ diff -a shfiles{,2}.zip | strings | grep '^[<>]'
> <       top -n 1 | grep Cpu.s | grep -o '[^ ]*.id' #| sed s/[^0-9]//g
>>       THIS IS BORKEN CHANGE top -n 1 | grep Cpu.s | grep -o '[^ ]*.id' #| 
>> sed s/[^0-9]//g
>
> ar is gives nicer diffs:
>
> $ diff -a shfiles{,2}.zip | wc
>     30     104    1154
> $ diff -a {1,2}.ar | wc
>      8      54     300
>
> $ diff -a {1,2}.ar
> 164c164
> < cooldown.sh/    1211341443  1000  1000  100644  469       `
> ---
>> cooldown.sh/    1211382850  1000  1000  100644  491       `
> 175c175
> <       top -n 1 | grep Cpu.s | grep -o '[^ ]*.id' #| sed s/[^0-9]//g
> ---
>>       THIS IS BORKEN CHANGE top -n 1 | grep Cpu.s | grep -o '[^ ]*.id' #| 
>> sed s/[^0-9]//g
>
>
> It seems as if we could probably even merge the diff if different sub
> files were changes. Still seems unsatisfying, as most likely in both
> zip/ar files the base .lyx file would have been changed.

Never tried this. This is impressive.

>> This is not needed. In my proposal, plain text, base64 format is used
>> without compression, and our existing compression feature is used to
>> compress this file.
>
> Storing embedded files as base64 text in the zip file would eliminate
> most of the advantages of the zip format discussed.

I started to see what you are saying. Use base64 for uncompressed
case, AND zip for compressed case. I have to admit this is a very
interesting proposal. I am taking a note. :-)

Bo

Reply via email to