Talk:Data Compression/Dictionary compression

rename
I suggest rename: "Data Compression/Library/Dictionaries" to "Data Compression/Dictionary compression".

I see that "library" is very frequently used with data compression -- but I only see it used in the sense of a software library. Any particular data compression algorithm can be implemented in a "data compression library". Is there some other "library compression" I am overlooking?

I see that "dictionary compression" is a specific category of data compression algorithms, somewhat complementary to "entropy coding" and "Markov compression" and "fractal compression", etc. --DavidCary (talk) 06:16, 9 September 2009 (UTC)


 * I don't know the rational that lead to the creation of the page (the user in unregistered so my bet is that we will never know), but I put forward that there can indeed be missing page about libraries in general (as a reference to other reference datasets besides dictionaries, even if I can't recall special distinctions, probably references table or caches, here the use of the word library isn't a reference to programming libraries), especially if the book will cover compression protocols for telecommunications. The page name was probably derived by a red link on the toc or/and the intention to use the automatically generated navigation scheme between close related pages, the same issue can be extended to the Order/Entropy page. Not stating an opinion only an observation.
 * I truly like the simplicity of how subpages facilitate navigation and turn navigational templates obsolete, so if you aren't adamantly against the concept see if altering the TOC and renaming the sections would satisfy...
 * One observation I make is that the book is poorly named, since it only focus on digital compression, the scope doesn't seem to cover signal or analog data. IIRC the Huffman encoding (the base for the LZ algorithm) and FAX image compression uses a symbolic table/library/dictionary to compress the transmission. A good substitution to the word "library" would be "dataset". --Panic (talk) 06:51, 9 September 2009 (UTC)


 * we will never know ? I know User:Graeme E. Smith says he created it.
 * here the use of the word library isn't a reference to programming libraries ? Is that so? Then may I ask: to what is it a reference? Allow me to repeat my earlier question: Any particular data compression algorithm can be implemented in a "data compression library". Is there some other "library compression" I am overlooking? Is it merely a synonym for "dictionary compression"?
 * the book is poorly named ... the scope doesn't seem to cover signal or analog data. ? I don't understand. Music and photographs are "analog data", right? Are you saying that this "Data Compression" book should *not* discuss analog data compression, and so we should delete the sections at Data Compression that discuss music and photograph compression?
 * p.s.: Huffman encoding is not the base for the LZ algorithm. Hopefully someday this book will make that clear. :-) --DavidCary (talk) 23:58, 9 September 2009 (UTC)


 * :) Well I didn't know that I only looked at the page history...
 * As I said above the word library could probably refer to different datasets (among other suppositions I refereed), those dataset aren't only restricted to dictionaries, sometimes the algorithms talks about several types of tables, alphabets and other data structures. But a library section would be cool too, covering programming libraries and distinctions among the algorithms they implement.
 * I hadn't read the book (and I haven't contributed content to it, so all this comments are made as by point reader). For what I examined most of it seemed to deal only with digital data, now that you mentioned the audio section does mention analog and signals (but not the image section).
 * As a reader I have a special interest on this book (and I have some background knowledge on the subject, mostly on the side of telecommunications). As an implementer (I'm writing a p2p app.) and possible future contributor, I'm interested in some algorithms, especially if they have free and tested implementations (LZF, LZWA as in the 7z SDK and others) from the point of bandwidth savings/and their overall system footprint, those and any other algorithm that can optimize and reduce queries against content (FastBit etc). I may contribute something on those lines later on. --Panic (talk) 01:53, 10 September 2009 (UTC)

miniLZO
it just says: 'miniLZO: ...' 87.244.68.68 (talk) 00:45, 19 November 2010 (UTC)