RTF Pocket Guide

Errata for RTF Pocket Guide

Submit your own errata for this product.

The errata list is a list of errors and their corrections that were found after the product was released. If the error was corrected in a later version or reprint the date of the correction will be displayed in the column titled "Date Corrected".

The following errata were submitted by our customers and approved as valid errors by the author or editor.

Color key: Serious technical mistake Minor technical mistake Language or formatting error Typo Question Note Update

Version Location Description Submitted By Date submitted Date corrected
Nowhere in particular

This book is missing two things that most O'Reilly books have: a note about
the cover animal, and a thank-you list of the various people who helped out
with the book. So, here it is, better late than never:

* The cover animal is a tegu, an iguana-like lizard that is remarkable
because it is large (about the size of a housecat), it swims, and it has
amazing coloration and patterns in its skin. After careful thought, we
have named the coverlizard "Juche".

* A bunch of people helped a lot with getting this book out, and I'm sorry
that I didn't thank them in print. First off, there's my superstah of an
editor, Linda Mui, as well as all the staff at O'Reilly who put extra care
and effort into everything they do. You have /no/ idea how many people had
to be on the ball to get the book from my computer to your hands!
And then there's the tech editors, the folks who read my manuscript and
made sure it was accurate and clear, and told me when it wasn't:
Paul DuBois
David Hand
Robert Rothenberg
Peter Sergeant
Ken Williams
Each helped me in his own specially skilled way by doing everything from
catching typoes, to suggesting better ways to explain tricky concepts, to
advising me when I was uncertain whether a particular subtopic needed to be

page 6, page 36, and page 127
On those pages, I'm slightly unclear about the character-range that is
added to Latin-1 to produce the "ANSI" character set. So here is the

ANSI adds a character at codepoint 128, and a character at codepoint 159,
and more characters at a bunch of codepoints inbetween. But while ANSI is
giving you a whole block of new characters, it takes away the codepoints
127 and 160!

Latin-1 codepoint 127 is the delete character -- you'll just have to do
without that in RTF, somehow, somehow. Latin-1 codepoint 160 is the
non-breaking space character -- just use \~ to get that, (instead of
\'a0). Lo, verily, the large print giveth, and the small print taketh away.

Page 18

This codeblock is missing a "}" at the end.

Page 21
First paragraph

The RTF code is li2160 and i2160, but the margins in the picture are 2180 and 2150.
Change li2160 to li2180
change i2160 to i2150

Page 29
Last bulleted paragraph

Text says that "favorite" will be bolded, but both code samples bold "very favorite".

Page 32
end of last line on page

Missing a closequote before the period.

Page 40
third paragraph

Correct "entry 4a" to "entry 4". (There can't be such thing as an
"entry 4a" in a color table!)

Page 53
Second paragraph under Newspaper Columns

"A layout with newspaper columns is can make pages with small print or frequent linebreaks much easier to read."
should say:
"A layout with newspaper columns can make pages with small print or frequent linebreaks much easier to read."

Page 55
throughout the page

Correct all cases of "sectdsect" to "sectsectd".

Page 62
End of first paragraph under "Embedding Images"

I say:
But the picture data encoded in the {pict...} construct is in a binary
format that can't be converted to easily from a conventional image
format (i.e., GIF, JPEG, or PNG).

This is true for GIFs, but untrue for JPEGs and PNGs. That is, you can't
easily embed GIFs, but you /can/ easily embed JPEGs and PNGs, using the
{pictjpegblippicwXpichY...} or {pictpngblippicwXpichY...}
constructs, and embedded hex data.

I discuss this in detail, with examples, in the images_in_rtf directory of
the book's code archive.

Page 65
figure 15

I note that a production slave, in an earnest attempt to save space,
cropped whitespace out of this illustration, oblivious to the fact that
the whitespace is WHAT MAKES IT A CENTERED PAGE. So either use your
imagination, or just open the 065_vhcenter.rtf in the code archive at
this book's web site.

Page 110
last comment-line in the "sub esc" routine

The reference to "Appendix A" should be to the section "Unicode in RTF",
on page 33.

(If you're curious, at the last minute, the book was rearranged and what
had been appendices A-F were moved around. The short little Appendix A
was moved to page 33-35; App B became Part II, "Creating MSWindows Help
Files"; Apps C,D, and E became Part IV "Reference Tables"; and Appendix
F became Part III, "Example Programs". This all improved the flow of
the book, but we did miss this reference on page 110 and 120!)

Page 120
last comment-line in the "sub esc" routine

The reference to "Appendix A" should be to the section "Unicode in RTF",
on page 33.

Page 123
codeblock, comment line in sub unesc

To the end of this line:
# resolve escapes like \'b1 for
...add the plusminus character
(The final plusminus character was lost during production, in spite of
my production note saying 'PRODUCTION: the last character in the line
"sub unesc..." is a plusminus symbol!!'. Oops.)