One can read only so much before it comes time to join a discussion and ask some questions. There are two major venues for discussions about CSS, but each is concerned with a specific type of discussion -- so make sure you go to the right place.
This Usenet group, often abbreviated as ciwas (pronounced "see-wass"), is the gathering place for CSS authors. A number of experts in the field check this newsgroup regularly, this author among them, and all are there for one primary reason: to help new CSS authors over the hurdles that learning any new language will generate. The secondary reason is for the spirited debates that occasionally erupt over some aspect of CSS, or a browser's implementation thereof. Rather unusually for a newsgroup, the signal-to-noise ratio stayed fairly high for the last few years of the 1990s, and will with any luck continue in that vein.
Anyone who wishes to be involved in discussing the future course of CSS, and to clearing up ambiguities in the specifications, should subscribe to this list. The members of the list are all, in one fashion or another, interested in making CSS better than it is already. Please note: www-style is not the place to ask for assistance with writing CSS. For help with CSS authoring problems, visit ciwas instead. Questions beginning with "How do I ... ?" are frowned upon by the regulars of www-style and are usually redirected to a more appropriate forum such as ciwas. On the other hand, questions that begin "Why can't I ... ?" or "Wouldn't it be cool if ... ?" are generally welcome, so long as they relate to some ability that appears to be missing from CSS.
Messages to www-style are only accepted if the sender is already subscribed to the list. In order to subscribe, send email to firstname.lastname@example.org with the word subscribe in the subject of the message; to unsubscribe, send email to email@example.com with the word unsubscribe in the subject of the message.
Another solution is to set the styles such that lines are no taller than absolutely necessary to hold their content. This is where you might use a line-height of 1.0. This value will multiply itself by every font-size to get the same value as the font-size of every element. Thus, for every element, the inline box will be the same as the content area.
Copyright © 2002 O'Reilly & Associates. All rights reserved.or so pixels contain the "sidebar" image. The rest of theimage is basically wasted, as we can see in Figure 6-27.
Wouldn't it be much nicer to just create a sidebar image whichis 10 pixels tall and 100 pixels wide, with no wasted blank space,and then repeat it only in the vertical direction? This wouldcertainly make your design job a little easier, and your users'download times a lot shorter. Enterbackground-repeat. By not predefining any tags in the XML Recommendation, the W3C allowed developers full control over customizing their data as they see fit. This makes XML very attractive to encoding data that already exists in legacy databases (by using database metadata, and other schema information). This extensibility of XML makes it such a great fit when trying to get different systems to work with each other.
Since the structure of the XML document can be specified in DTDs they provide a simple way to make it easier to exchange XML documents that conform to a DTD. For example, if two software systems need to exchange information, then if both of the systems conform to one DTD, the two systems can process information from each other. DTDs are not as powerful as some kind of schema architecture for XML, they don't support typing, subclassing, or instantiation mechanisms that a schema architecture must have.
DTDs are a simple way to make sure that 2 or more XML documents are of the same "type". Its a very limited approach to making "typed" XML documents shareable across systems. In the future some kind of schema system will be proposed by the W3C that should allow typing, instantiation and inheritance of information (in XML).