Flylib.com

Books Software

 
 
 

Conventions Used in This Book

 < Day Day Up > 

Conventions Used in This Book

The following is a list of the typographical conventions used in this book:



Italics

Used to indicate URLs, filenames, filename extensions, and directory/ folder names . For example, a path in the filesystem will appear as / Developer/Applications.



Constant width

Used to show code examples, the contents of files, console output, as well as the names of variables , commands, and other code excerpts.



Constant width bold

Used to highlight portions of code, typically new additions to old code.



Constant width italic

Used in code examples and tables to show sample text to be replaced with your own values.



Color

The second color is used to indicate a cross-reference within the text.

You should pay special attention to notes set apart from the text with the following icons:

This is a tip, suggestion, or general note. It contains useful supplementary information about the topic at hand.


This is a warning or note of caution, often indicating that your money or your privacy might be at risk.


The thermometer icons, found next to each hack, indicate the relative complexity of the hack:

beginner moderate expert

 < Day Day Up > 
 < Day Day Up > 

Using Code Examples

This book is here to help you get your job done. In general, you may use the code in this book in your programs and documentation. You do not need to contact us for permission unless you're reproducing a significant portion of the code. For example, writing a program that uses several chunks of code from this book does not require permission. Selling or distributing a CD-ROM of examples from O'Reilly books does require permission. Answering a question by citing this book and quoting example code does not require permission. Incorporating a significant amount of example code from this book into your product's documentation does require permission.

We appreciate, but do not require, attribution. An attribution usually includes the title, author, publisher, and ISBN. For example: " Digital Video Hacks by Joshua Paul. Copyright 2005, O'Reilly Media, Inc., 0596009461."

If you feel your use of code examples falls outside fair use or the permission given above, feel free to contact us at permissions@oreilly.com.

 < Day Day Up > 
 < Day Day Up > 

How to Contact Us

We have tested and verified the information in this book to the best of our ability, but you may find that features have changed (or even that we have made mistakes!). As a reader of this book, you can help us to improve future editions by sending us your feedback. Please let us know about any errors, inaccuracies, bugs , misleading or confusing statements, and typos that you find anywhere in this book.

Please also let us know what we can do to make this book more useful to you. We take your comments seriously and will try to incorporate reasonable suggestions into future editions. You can write to us at:

O'Reilly Media, Inc.
1005 Gravenstein Hwy N.
Sebastopol, CA 95472
(800) 998-9938 (in the U.S. or Canada)
(707) 829-0515 (international/local)
(707) 829-0104 (fax)

To ask technical questions or to comment on the book, send email to:

bookquestions@oreilly.com

The web site for Digital Video Hacks lists examples, errata, and plans for future editions. You can find this page at:

http://www.oreilly.com/catalog/digitalvideohks/

For more information about this book and others, see the O'Reilly web site:

http://www.oreilly.com
 < Day Day Up >