Figures 10.9, 10.10, 10.11: the BER actually shown is 1e-9; caption should
be changed from 1e-6 to 1e-9.
Version 1.1.2:
E-book formatting issues; no changes to printed version.
Version 1.1.3:
Added to glossary: Longitudinal Redundancy Check (LRC): a
single-sum checksum using an XOR operation rather than integer addition
Clarification on page 43, Table 4.1 caption: "Gray highlighting is
just for row delineation."
Clarification on page 149: After "This is slightly awkward because it
frees up two bits in the check value", add "(one bit for each of SumA
and SumB)"
Clarification on page 150: "One of these is filled with that
calculated parity bit"=> "One of these is filled with a parity bit
calculated over both the data word and rest of the check value"
Clarification on page 183: "4-byte"=> "4-byte
(32-bit)"
Clarification on page 183: "23-byte"=> "23-byte
(184-bit)"
Page 255: 'all an "1"'=> 'an all "1"'
Pages 274-276, section 10.15.3.2. "BitCount(valuez)
<=2)"=> "BitCount(valuex) <=2)" in outer
loop of code snippets
Page 257 top of page: "behavior or shorter."=> "behavior
or shorter for polynomials not divisible by (x+1)."
Page 294 section 11.4.2: "detect all bursts less than the number of
bits in the check value"=> "detect any single burst fault up to k
bits in length for a k-bit check value"
Figure 11.11 caption: data is for a 130-byte code word
All figures in Chapter 11 and figure 12.1: added caption clarification of
"(Lower on vertical axis is better.)"
E-book hints:
The e-book should view fine on a monochrome display. However, the book
makes extensive use of color, so a color display will provide a better
experience.
If images seem small or text spacing looks weird, consider switching to
landscape orientation for that portion of the book. (We have converted most
space-sensitive text to images to avoid issues, but on small screens there can
still be some sections where landscape just works better.)
On some e-book readers pop-up footnotes do not have URL links active. If
you go to the "all footnotes" view the link will be there and will be
active. This is a reader issue and not something that can be fixed in the
e-book itself.
We have seen some odd number alignment behavior on Lithium viewer, but the
e-book passes the Smashwords validation test and it seems to be an issue with
that viewer rather than the e-book source files.
