GeneralThis forum is for non-technical general discussion which can include both Linux and non-Linux topics. Have fun!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
It's more or less the same, depending on the data internal structure. An implementation working on string also works for any other file content. GIF format is an example of LZW usage for binary data.
Algorithms such as LZW neither know nor care what the data to be compressed "means to you." (Computers can't read.)
It is a provable fact, of course, that text is much more compressible than binary data simply because text has much more redundancy (at the bitwise level). A typical file of English text, for instance, uses only a fraction (26+26+20 or so) of the 256 possible values of "a byte," which realistically means that only 6/8'ths of the bandwidth is being used under worst-case conditions. With binary data, the probability is much greater that most of the 256 possible values are being used. That is to say, within any given block of (say) 4096*8 bits, there aren't too many usefully-repeated groups of bits.
File-compression basically works by identifying repeated groups of bits, within a window of data of some length, and replacing them with a single (bitwise) code...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.