Typos in the text and bugs in the example code can be reported through our Bugzilla server. To use Bugzilla, you must create an account and provide a valid e-mail address. Your e-mail address will only be used for the purposes of bug tracking. We will not provide your address to third parties, nor will we use it for any purpose other than bug tracking.

If you have never used a Bugzilla system, don't worry: reporting a typo/bug using Bugzilla is extremely simple. Simply follow these steps:

• Create a new Bugzilla account in our Bugzilla server. You will only need to provide your name and a valid e-mail address. Your account password will be mailed to the e-mail address you provide.
• In the main page, select Enter a new bug report.
• If you are reporting a typo in the book, make sure you specify:
• The "version" of the book. This refers to the edition and printing of the book (some typos are corrected from one printing to another).
• Select the "Book typos" component. The "Assign to" field will be automatically filled in when you select the component.
• Use the default values for "Platform", "OS", "Priority", and "Severity".
• Write a summary and a description for the bug. In the summary, simply write a one-phrase description of the bug (e.g. "Typo in page 142"). In the description, provide the sentence where the typo is located and highlight the typo itself with asterisks (e.g. "To run this example, use the *folloiwng* command:")
• Leave "Depends on" and "Blocks on" blank.
• If you are reporting a bug in the examples, please specify the following:
• The "version" of the book. This refers to the edition and printing of the book (some typos are corrected from one printing to another).
• Select the "MathService examples" component or one of the "FileBuy" components. The "Assign to" field will be automatically filled in when you select the component.
• Select the appropriate "Platform" and "OS" (Bugzilla will make an educated guess).
• Specify the severity of the bug. For example, if you've found a bug that prevents an examples from being compiled or run, the bug should be labelled "major". If you've found a typo in one of the comments, it should be labelled "minor".
• Write a summary and a description for the bug. In the summary, simply write a one-phrase description of the bug (e.g. "Example FOOBAR generates incorrect EPR file"). In the description, give a detailed account of the bug. If you have found a fix, we would appreciate it if you include a patch.
• Unless you know what you're doing, leave "Depends on" and "Blocks on" blank.