view en/ch00-preface.xml @ 831:acf9dc5f088d

Add a skeletal preface.

<!-- vim: set filetype=docbkxml shiftwidth=2 autoindent expandtab tw=77 : -->

<preface id="chap:preface">
  <?dbhtml filename="preface.html"?>
  <title>Preface</title>

  <sect1>
    <title>Conventions Used in This Book</title>

    <para>The following typographical conventions are used in this
      book:</para>

    <variablelist>
      <varlistentry>
        <term>Italic</term>

        <listitem>
          <para>Indicates new terms, URLs, email addresses, filenames,
	    and file extensions.</para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><literal>Constant width</literal></term>

        <listitem>
          <para>Used for program listings, as well as within
	    paragraphs to refer to program elements such as variable
	    or function names, databases, data types, environment
	    variables, statements, and keywords.</para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><userinput>Constant width bold</userinput></term>

        <listitem>
          <para>Shows commands or other text that should be typed
	    literally by the user.</para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><replaceable>Constant width italic</replaceable></term>

        <listitem>
          <para>Shows text that should be replaced with user-supplied
	    values or by values determined by context.</para>
        </listitem>
      </varlistentry>
    </variablelist>

    <tip>
      <para>This icon signifies a tip, suggestion, or general
	note.</para>
    </tip>

    <caution>
      <para>This icon indicates a warning or caution.</para>
    </caution>
  </sect1>

  <sect1>
    <title>Using Code Examples</title>

    <para>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.</para>

    <para>We appreciate, but do not require, attribution. An
      attribution usually includes the title, author, publisher, and
      ISBN. For example: “<emphasis>Book Title</emphasis> by Some
      Author. Copyright 2008 O’Reilly Media, Inc.,
      978-0-596-xxxx-x.”</para>

    <para>If you feel your use of code examples falls outside fair use
      or the permission given above, feel free to contact us at
      <email>[e-mail]</email>.</para>
  </sect1>

  <sect1>
    <title>Safari® Books Online</title>

    <note role="safarienabled">
      <para>When you see a Safari® Books Online icon on the cover of
	your favorite technology book, that means the book is
	available online through the O’Reilly Network Safari
	Bookshelf.</para>
    </note>

    <para>Safari offers a solution that’s better than e-books. It’s a
      virtual library that lets you easily search thousands of top
      tech books, cut and paste code samples, download chapters, and
      find quick answers when you need the most accurate, current
      information. Try it for free at <ulink role="orm:hideurl:ital"
	url="http://my.safaribooksonline.com/?portal=oreilly">http://my.safaribooksonline.com</ulink>.</para>
  </sect1>

  <sect1>
    <title>How to Contact Us</title>

    <para>Please address comments and questions concerning this book
      to the publisher:</para>

    <simplelist type="vert">
      <member>O’Reilly Media, Inc.</member>

      <member>1005 Gravenstein Highway North</member>

      <member>Sebastopol, CA 95472</member>

      <member>800-998-9938 (in the United States or Canada)</member>

      <member>707-829-0515 (international or local)</member>

      <member>707 829-0104 (fax)</member>
    </simplelist>

    <para>We have a web page for this book, where we list errata,
      examples, and any additional information. You can access this
      page at:</para>

    <simplelist type="vert">
      <member><ulink url="http://www.oreilly.com/catalog/&lt;catalog
	  page&gt;"></ulink></member>
    </simplelist>

    <remark>Don’t forget to update the &lt;url&gt; attribute,
      too.</remark>

    <para>To comment or ask technical questions about this book, send
      email to:</para>

    <simplelist type="vert">
      <member><email>[e-mail]</email></member>
    </simplelist>

    <para>For more information about our books, conferences, Resource
      Centers, and the O’Reilly Network, see our web site at:</para>

    <simplelist type="vert">
      <member><ulink url="http://www.oreilly.com"></ulink></member>
    </simplelist>
  </sect1>
</preface>

<!--
local variables: 
sgml-parent-document: ("00book.xml" "book" "preface")
end:
-->