Compression of SVG(Z)s in git repositories

[Sebastian Kügler]

On Monday, September 01, 2014 12:59:04 Elias Probst wrote:
> I've noticed, that (except of only a very few) nearly all SVG files are
> committed as SVGZ to our git repositories.
> 
> This has IMHO several drawbacks:
> - every change will be stored as a single atomic blob
> - git's internal packfile compression and deduplication can't be used
> - no diffs for changes done to SVGs can be viewed
> - batch-editing of files via sed/awk/… is way more difficult
> 
> I'd like to suggest to implement a git hook which enforces SVG files
> being pushed uncompressed.
> The compression of SVG to SVGZ might happen when building release tarballs.
> 
> What are your thoughts? Any reasons not to do this?

Compressed SVG files are way faster to read (it's faster to decompress the 
data than to read it from disk). Also, the on-disk footprint is lower.

Both of these affect the runtime performance of Plasma.

Also, diffs of SVG are pretty useless, they're almost impossible to read for a 
human being.
-- 
sebas

http://www.kde.org | http://vizZzion.org | GPG Key ID: 9119 0EF9