Update
This commit is contained in:
parent
390c8b8a4c
commit
3d11ef05d8
36 changed files with 2003 additions and 1984 deletions
|
@ -19,9 +19,9 @@ The basic division of compression methods is to:
|
|||
- **lossless**: No information contained in the original data will be lost in the compressed data, i.e. the original file can be restored in its entirety from the compressed file.
|
||||
- **lossy**: Some information contained in the original data is lost during compression, i.e. for example a compressed image will be of slightly worse quality. This usually allows for much greater compression. Lossy compressors usually also additionally apply lossless compression as well.
|
||||
|
||||
Furthermore we may divide compression e.g. to offline (compresses a whole file, may take long) and streaming (compressing a stream of input data on-the-go and in real-time), by the type of input data (binary, text, audio, ...), basic principle ([RLE](rle.md), dictionary, "[AI](ai.md)", ...) etc.
|
||||
Furthermore we may divide compression for example to offline (compresses a whole file, may take long) and streaming (compressing a stream of input data on-the-go and in real-time), by the type of input data (binary, text, audio, ...), basic principle ([RLE](rle.md), dictionary, "[AI](ai.md)", ...) etc.
|
||||
|
||||
The following is an example of how well different types of compression work for an image (screenshot of main page of Wikimedia Commons, 1280x800):
|
||||
What follows is an example of how well different types of compression work for an image (screenshot of main page of Wikimedia Commons, 1280x800):
|
||||
|
||||
{ Though the website screenshot contained also real life photos, it still contained a lot of constant color areas which can be compressed very well, hence quite good compression ratios here. A general photo won't be compressed as much. ~drummyfish }
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue