|
|
|
To help you get the most from the text and keep track of what's happening, we've used a number of conventions throughout the book.
For instance:
| Important |
These boxes hold important, not to be forgotten information, which is directly relevant to the
While the background style is used for asides to the current discussion. |
As for styles in the text:
When we introduce them, we highlight important words
We show keyboard strokes like this: Ctrl-K
We show filenames and code within the text like so: < element >
Text on
We present code in two different ways:
In our code examples, the code foreground style shows new, important, pertinent code while code background shows code that is less important in the present context or has been seen before.
|
|
|
|
|
|
We always value hearing from our readers and
we want to know what you think about this book: what you
|
|
|
|
|
|
We've made every effort to make sure that
there are no errors in the text or in the code. However, no one is
perfect and mistakes do occur. If you find an error in one of our
books, like a spelling mistake or faulty piece of code, we would be
very grateful for your feedback. By sending in errata you may save
other reader hours of frustration, and of course, you will be
helping us provide even higher quality information. Simply e-mail
the information to
support@wrox.com
;
your information will be checked and if appropriate, posted to the
errata page for that title or used in
To find errata on the web site, go to http://www.wrox.com/ , and simply locate the title through our Search or title list. Click on the View errata link, which is below the cover graphic on the book's detail page.
|
|
|
|
|
|
If you wish to directly query a problem in the book with an expert who
The title of the book , last four digits of the ISBN (5814) , and page number of the problem in the Subject field.
Your
We won't send you junk mail. We need the details to save your time and ours. When you send an e mail message, it will go through the following chain of support:
Customer Support – Your message will be delivered to our customer support, and they will be the first people to read it. They have files on the most frequently asked questions and will answer anything general about the book or the web site immediately.
Editorial – Deeper queries are forwarded to the technical editor responsible for that book. They have experience with the programming language or a particular product, and are able to answer detailed technical questions on the subject.
The Authors – Finally, in the
The Wrox support process can only offer help on issues directly pertinent to the content of our published title. Answers to questions that fall outside the scope of normal book support may be obtained through the community lists of our http://p2p.wrox.com/ forum.
|
|
|