1984
DOI: 10.1109/tit.1984.1056931
|View full text |Cite
|
Sign up to set email alerts
|

Self-synchronizing Huffman codes (Corresp.)

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
62
0

Year Published

1994
1994
2020
2020

Publication Types

Select...
5
3

Relationship

0
8

Authors

Journals

citations
Cited by 154 publications
(62 citation statements)
references
References 6 publications
0
62
0
Order By: Relevance
“…This leads to a loss of around 3 percentage points in compression ratio, but makes TH a fast self-synchronizing code, 8 which can be directly 8 That is, it is possible to detect quickly the beginning of searched for a compressed pattern with any string matching algorithm. While most Huffman codes have the property of self-synchronization [17], this may require processing an arbitrary number of codewords. Some compressors introduce synchronization strings or marks to force the resynchronization after a given number of bits/bytes [18,19].…”
Section: Word-based Text Compressionmentioning
confidence: 99%
See 1 more Smart Citation
“…This leads to a loss of around 3 percentage points in compression ratio, but makes TH a fast self-synchronizing code, 8 which can be directly 8 That is, it is possible to detect quickly the beginning of searched for a compressed pattern with any string matching algorithm. While most Huffman codes have the property of self-synchronization [17], this may require processing an arbitrary number of codewords. Some compressors introduce synchronization strings or marks to force the resynchronization after a given number of bits/bytes [18,19].…”
Section: Word-based Text Compressionmentioning
confidence: 99%
“…17 • The Re-pair 18 compressor coupled with a bitoriented Huffman. 19 • Gnu gzip, 20 a Ziv-Lempel-based compressor.…”
Section: Boosting Compressionmentioning
confidence: 99%
“…For certain distributions, a Huffman code may be constructed that includes synchronizing codewords or sequences [19,20]. These are codewords or sequences after the occurrence of which decoding will be correct, regardless of any possible error before them.…”
Section: Synchronizationmentioning
confidence: 99%
“…This is a data source that is known to have highly variable data lengths from block to block. Values for pk(x) and qk(x) have been found by iterative use of (4) and (5). From this, a prediction of the number of bits still to be placed at stage 5 has been found.…”
Section: A Bit Placementmentioning
confidence: 99%
“…This is idue to errors that cause the decoder to lose synchronization with the start and end of blocks. Even in codes where synchronization is regained after the loss of a few blocks [4], [5], the block count is likely to be permanently offset, resulting in the following data being decoded at the wrong location. For some applications, e.g., speech, this may not be a problem as it may only cause a temporal shift in the following data.…”
mentioning
confidence: 99%