Lines Matching full:abbreviations
21 <li><a href="#abbreviations">Abbreviations</a></li>
77 provides a mechanism for the file to self-describe "abbreviations", which are
109 <li>Abbreviations, which specify compression optimizations for the file.</li>
288 <li>A set of abbreviations. Abbreviations may be defined within a block, in
290 enclosing blocks see the abbreviation). Abbreviations can also be defined
299 its own set of abbreviations, and its own abbrev id width. When a sub-block is
393 encoded according to the <a href="#abbreviations">abbreviation definition</a>.
398 abbreviations is defined below.
412 <a name="abbreviations">Abbreviations</a>
417 Abbreviations are an important form of compression for bitstreams. The idea is
425 Abbreviations can be determined dynamically per client, per file. Because the
426 abbreviations are stored in the bitstream itself, different streams of the same
427 format can contain different sets of abbreviations according to the needs
444 defined abbreviations in the scope of this block. This definition only exists
446 blocks. Abbreviations are implicitly assigned IDs sequentially starting from 4
447 (the first application-defined abbreviation ID). Any abbreviations defined in a
450 abbreviations defined within the block itself. Abbreviated data records
598 <tt>BLOCKINFO</tt> block itself. The abbreviations defined
614 "metadata," the abbreviations they contain are essential for parsing records
665 descriptions, etc. This document does not describe the set of abbreviations
