Book HomeCascading Style Sheets: The Definitive GuideSearch this book Wednesday 30th of July 2014 07:10:30 PM

0.3. 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!). Please let us know about any errors you find, as well as your suggestions for future editions, by writing to:

O'Reilly & Associates, Inc.

1005 Gravenstein Highway North

Sebastopol, CA 95472

(800) 998-9938 (in the U.S. or Canada)

(707) 829-0515 (international/local)

(707) 829-0104 (fax)

You can also send us messages electronically. To be put on the mailing list or request a catalog, send email to: feel for an entire corporate web site. Our main goal is to createstyles that are as simple as possible, using few (if any) classes orIDs. For the purposes of the project, we will assume there is astandard writing guide for employees of the company: document titlesare in H1, subheadings in H2,every page uses standard graphics at the top, and so forth.

Marketing has decreed that all pages shall use a white backgroundwith a thin dark green stripe running down the left edge, black bodytext in a serif font, and hyperlinks that are a dark green when

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

We have a web site for the book, where we'll list examples, errata, and any plans for future editions. You can access this page at:

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

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

http://www.oreilly.com/



Library Navigation Links

Copyright © 2002 O'Reilly & Associates. All rights reserved.

P {margin-left: 100px; margin-right: 100px; width: auto;}
Figure 8-13

Figure 8-13. Automatic width

This is the most common case, in fact, since it is equivalent to setting the margins and not declaring anything for the width. The result of this markup is exactly the same as that shown in Figure 8-13:

P {margin-left: 100px; margin-right: 100px;} /* same as before */

WARNING

You can generate the XML yourself (from your object model). If you created an object model that simply imports information from your XML document (using SAX or DOM), you would have to write a class that would convert your object model into an XML file (or set of XML files). This class would have to create an ApplicationML file that contains the information in your Java object model (which is in memory). Since this object model is not an adapter on top of DOM, it is not possible to use the DOM parser to generate the XML for you.
  • You can use the DOM parser to generate the XML for you if you created an object model that is an adapter on top of DOM. Since your object model uses the document object tree, all the information contained in it is actually stored in the tree. The XML parser can take this tree and convert it to XML for you, you can then save this generated XML to a file. So the DOM parser can generate the ApplicationML file for you.
  • There are advantages and disadvantages to using some of the strategies to import and export XML. The complexity of your application data and available system resources are factors that would determine what strategy should be used.

    Client and Server side - Application Servers

    <P STYLE="font-size: 12px; line-height: 12px;">
    This is text, <EM>some of which is emphasized</EM>, plus other text<BR>
    which is <B STYLE="font-size: 24px;">boldfaced</B> and which is<BR>
    larger than the surrounding text.
    </P>

    What we have here is a situation where some of the text has a font-size of 12px , while other text has a size of 24px . However, all of the text has a line-height of 12px,