<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Design&gt;Web Design&gt;XHTML</title>	<link>http://tc.eserver.org/dir/Design/Web-Design/XHTML</link>
	<description>A listing of the most recently indexed works about Design and Web Design and XHTML in the field of technical communication.</description>
	<language>en-us</language>
	<copyright>Copyright (c) 2005-08 by the EServer. All rights reserved.</copyright>
	<managingEditor>tclib-editorial@eserver.org (TC Library Editorial Board)</managingEditor>
	<webMaster>webmaster@eserver.org (Geoffrey Sauer)</webMaster>
	<image>
		<url>http://tc.eserver.org/images/newlogo.gif</url>
		<title>Design&gt;Web Design&gt;XHTML</title>
		<link>http://tc.eserver.org/dir/Design/Web-Design/XHTML</link>
	</image>
	<item>
		<title>XHTML Cheat Sheet</title>
		<link>http://tc.eserver.org/34762.html</link>
		<guid>http://tc.eserver.org/34762.html</guid>
		<description>This XHTML cheat sheet is excellent for XHTML coders. Along with many basic attributes, this two-page grid includes references that even experienced web professionals would find useful.&#xD;&#xD;Three types of elements are defined in this cheat sheet: block, inline and table elements. The miscellaneous section includes 22 additional elements. Each row contains the name, description and attributes of each of the elements available for use.</description>
	</item>
	<item>
		<title>Recommended List of DTDs You Can Use in Your Web Document</title>
		<link>http://tc.eserver.org/34737.html</link>
		<guid>http://tc.eserver.org/34737.html</guid>
		<description>When authoring document is HTML or XHTML, it is important to Add a Doctype declaration. The declaration must be exact (both in spelling and in case) to have the desired effect, which makes it sometimes difficult. To ease the work, below is a list of recommended declarations that you can use in your Web documents.</description>
	</item>
	<item>
		<title>The Road to XHTML 2.0: MIME Types</title>
		<link>http://tc.eserver.org/34149.html</link>
		<guid>http://tc.eserver.org/34149.html</guid>
		<description>Here&apos;s a dirty little secret: browsers aren&apos;t actually treating your XHTML as XML. Your validated, correctly DOCTYPE&apos;d, completely standards compliant XHTML markup is being treated as if it were still HTML with a few weird slashes in places they don&apos;t belong (like &lt;br /&gt; and &lt;img /&gt;). Why? The answer is MIME types.</description>
	</item>
	<item>
		<title>Common Ideas Between HTML and XHTML</title>
		<link>http://tc.eserver.org/34002.html</link>
		<guid>http://tc.eserver.org/34002.html</guid>
		<description>As of this writing, HTML and XHTML are both being used to create Web sites. But there are multiple versions of each, with specific changes and ideas attached. The following table shows the current W3C HTML and XHTML recommendations of note.</description>
	</item>
	<item>
		<title>HTML Versus XHTML: Which Should We Use, and Why?</title>
		<link>http://tc.eserver.org/34006.html</link>
		<guid>http://tc.eserver.org/34006.html</guid>
		<description>HTML 4.01 is as valuable as XHTML 1.0 in a daily usage. The syntax proposed by XHTML 1.0 has several important benefits. The weight of these benefits has to be evaluated in the context of your project: Use the right tool for the right job.&#xD;&#xD;For a Web designer, starting to use XHTML 1.0 will be helpful in some circumstances and will certainly help you to smoothly negotiate the future. XHTML 1.0 gives a wonderful opportunity to learn about XML languages and their possibilities without having to learn new semantics because you’re working with familiar tags and attributes.</description>
	</item>
	<item>
		<title>XSL(T) Tools for XHTML</title>
		<link>http://tc.eserver.org/34007.html</link>
		<guid>http://tc.eserver.org/34007.html</guid>
		<description>One of the great things about XHTML is that it combines the well-known power of HTML as an hypertext markup language with the power of the tools developed to work on XML documents. Among those tools, one of the most ubiquitous technology developed for XML is the Extensible Style sheet Language (XSL), and especially its Transformation language that allows to transform a given XML document in another XML document with a set of declarative rules. This document lists a set of style sheets that takes advantage of XHTML being an XML language to make your XHTML documents more re-usable.</description>
	</item>
	<item>
		<title>Prototyping with XHTML</title>
		<link>http://tc.eserver.org/33312.html</link>
		<guid>http://tc.eserver.org/33312.html</guid>
		<description>Looking for another way of realizing your design deliverables? XHTML are easy to code, can double as specifications, and create constraints that increase design effectiveness.</description>
	</item>
	<item>
		<title>The Sagacity in Validation</title>
		<link>http://tc.eserver.org/32957.html</link>
		<guid>http://tc.eserver.org/32957.html</guid>
		<description>In one of my introductory articles I stated that I do not care much for validation, yet I use well-formed XHTML 1.0 Strict (no less) as my preferred standard and CSS for layout purposes. If so, why on earth would I claim not to care about, or ignore, validation?</description>
	</item>
	<item>
		<title>Web Design Going in the Wrong Direction?</title>
		<link>http://tc.eserver.org/32958.html</link>
		<guid>http://tc.eserver.org/32958.html</guid>
		<description>There’s way too much talk about CSS and XHTML and Standards and Accessibility and not enough talk about people. CSS and Standards Compliant Code are just tools — you have to know what to build with these tools.</description>
	</item>
	<item>
		<title>Web Development Mistakes</title>
		<link>http://tc.eserver.org/32959.html</link>
		<guid>http://tc.eserver.org/32959.html</guid>
		<description>When I visit a website, especially if it’s the site of a competitor or a prospective client, I like viewing source and take a look at what’s under the hood. It’s one of my not-so-secret obsessions. And I am way too often absolutely disgusted by what I see. The web is overflowing with sites that use horribly invalid, broken, and inaccessible markup.</description>
	</item>
	<item>
		<title>What’s the Difference Between HTML and XHTML?</title>
		<link>http://tc.eserver.org/32744.html</link>
		<guid>http://tc.eserver.org/32744.html</guid>
		<description>If you’ve mastered HTML, you’re 90% of the way towards using XHTML. They’re actually very much the same thing—tag-based markup languages used to display Web pages. The difference is only seen by the people creating the pages (Web designers, programmers, etc.) and focuses on “forgivability”— HTML allows for some ugly code (mixed case tags like &lt;BoDy&gt;, improperly nested elements, and unclosed tags), while XHTML does not. If you write HTML, it’s probably a good idea to start using XHTML practices anyway. It will take 5 minutes to learn, and it’s just a better way of doing things.</description>
	</item>
	<item>
		<title>Building a More Semantic Web With Microformats</title>
		<link>http://tc.eserver.org/32626.html</link>
		<guid>http://tc.eserver.org/32626.html</guid>
		<description>This paper will introduce the Semantic Web, the next stage in the development of the web. We will explain why semantics are important, how they can help computers catalogue data, and how this will benefit us as individuals. We will also look at microformats, an ongoing project the aims to help us create a more semantic web. We assume you have a good knowledge of XHTML.</description>
	</item>
	<item>
		<title>Use Only Block-Level Elements in Blockquotes</title>
		<link>http://tc.eserver.org/32500.html</link>
		<guid>http://tc.eserver.org/32500.html</guid>
		<description>The blockquote element is not allowed to have text or inline elements as direct descendants. Only block-level (and in HTML 4.01 Strict, script) elements are allowed unless you use a Transitional Doctype, in which case both block-level and inline elements are allowed. But there are plenty of sites that use a Strict Doctype and still have blockquote elements that contain inline elements.</description>
	</item>
	<item>
		<title>The Basics of HTML</title>
		<link>http://tc.eserver.org/32437.html</link>
		<guid>http://tc.eserver.org/32437.html</guid>
		<description>In this article you will learn the basics of HTML—what it is, what it does, its history in brief, and what the structure of an HTML document looks like.</description>
	</item>
	<item>
		<title>The Trouble with Web Standards</title>
		<link>http://tc.eserver.org/30650.html</link>
		<guid>http://tc.eserver.org/30650.html</guid>
		<description>You may mistrust web standards because of bad experiences with buggy browsers. Or you might have converted a site from HTML to XHTML, only to discover that their layouts suddenly looked different in standards-compliant browsers. Don&apos;t give in to the dark side! Web standards are here to stay.</description>
	</item>
	<item>
		<title>Web &quot;Microformats&quot;</title>
		<link>http://tc.eserver.org/29986.html</link>
		<guid>http://tc.eserver.org/29986.html</guid>
		<description>Microformats is a term used to describe the storage of information using simple markup variations within existing markup languages. To a certain extent, microformats describes a methodology or philosophy, and comprises a set of design principles. Microformats is not a new language. It is usually a permutation of XHTML.&#xD;&#xD;The philosophy of microformats involves storing data in human-readable formats which are also machine-readable, but the emphasis is on the humans! Information tends to be visible, rather than hidden metadata.</description>
	</item>
	<item>
		<title>XHTML and the Escape Codes</title>
		<link>http://tc.eserver.org/29983.html</link>
		<guid>http://tc.eserver.org/29983.html</guid>
		<description>But one of the lesser known differences between HTML and XHTML is that attributes within tags (such as the href attribute within a link &lt;a&gt; tag) must use &apos;entities&apos; for special reserved characters. For example, within mark-up, &amp; has a special meaning. Greater than and less than signs (&gt; and &lt;) also have a special meaning, as they are used to define tags.</description>
	</item>
	<item>
		<title>Download our Site Template and Make the Leap to XHTML and CSS2</title>
		<link>http://tc.eserver.org/29329.html</link>
		<guid>http://tc.eserver.org/29329.html</guid>
		<description>If you face a Web site redesign or need a head start on your development efforts, our free Dreamweaver MX XHTML and CSS2 template may come in handy. Download the template and see how XHTML and CSS2 can reduce coding time and increase site accessibility.</description>
	</item>
	<item>
		<title>Put XHTML 1.0 Strict and Transitional to Work</title>
		<link>http://tc.eserver.org/29327.html</link>
		<guid>http://tc.eserver.org/29327.html</guid>
		<description>As its name suggests, XHTML--which is considered the successor to HTML 4--is a combination of HTML and XML. By combining the power of XML and HTML, XHTML makes Web content more accessible to devices such as phones, handhelds, and televisions. XHTML 1.0 is broken up into what the W3C refers to as three flavors: Strict, Transitional, and Frameset. In this article, I focus on the two most useful, Strict and Transitional.</description>
	</item>
	<item>
		<title>What XHTML Means for Wireless Development</title>
		<link>http://tc.eserver.org/29328.html</link>
		<guid>http://tc.eserver.org/29328.html</guid>
		<description>XHTML is emerging as the content-authoring language for wireless development, so you&apos;ll need to have a strong grasp of XHTMLMod and XHTML Basic. See what you need to know about the changing wireless development landscape.</description>
	</item>
	<item>
		<title>XHTML 1.1: Module-Based XHTML</title>
		<link>http://tc.eserver.org/28348.html</link>
		<guid>http://tc.eserver.org/28348.html</guid>
		<description>This Recommendation defines a new XHTML document type that is based upon the module framework and modules defined in Modularization of XHTML [XHTMLMOD]. The purpose of this document type is to serve as the basis for future extended XHTML &apos;family&apos; document types, and to provide a consistent, forward-looking document type cleanly separated from the deprecated, legacy functionality of HTML 4 [HTML4] that was brought forward into the XHTML 1.0 [XHTML1] document types. This document type is essentially a reformulation of XHTML 1.0 Strict using XHTML Modules. This means that many facilities available in other XHTML Family document types (e.g., XHTML Frames) are not available in this document type. These other facilities are available through modules defined in Modularization of XHTML, and document authors are free to define document types based upon XHTML 1.1 that use these facilities (see [XHTMLMOD] for information on creating new document types).</description>
	</item>
	<item>
		<title>XHTML Modularization 1.1</title>
		<link>http://tc.eserver.org/28347.html</link>
		<guid>http://tc.eserver.org/28347.html</guid>
		<description>This document is version 1.1 of XHTML Modularization, an abstract modularization of XHTML and implementations of the abstraction using XML Document Type Definitions (DTDs), and XML Schemas. This modularization provides a means for subsetting and extending XHTML, a feature needed for extending XHTML&apos;s reach onto emerging platforms. This specification is intended for use by language designers as they construct new XHTML Family Markup Languages. This specification does not define the semantics of elements and attributes, only how those elements and attributes are assembled into modules, and from those modules into markup languages. This second version of this specification includes several minor updates to provide clarifications and address errors found in the first version. It also provides an implementation using XML Schemas.</description>
	</item>
	<item>
		<title>Long Live the Q Tag</title>
		<link>http://tc.eserver.org/28240.html</link>
		<guid>http://tc.eserver.org/28240.html</guid>
		<description>IE/Win does not render these quotation marks, and because of this, most web authors choose not to use the Q tag. I&apos;m here to change all that!</description>
	</item>
	<item>
		<title>A Standardista&apos;s Alphabet</title>
		<link>http://tc.eserver.org/28241.html</link>
		<guid>http://tc.eserver.org/28241.html</guid>
		<description>The Lesser (or Badged) Standardista will include badges on their site to indicate which level of automated testing their site has passed, whereas the Greater (or Smug) Standardista frowns on the use of badges, and insists on double-checking every checkpoint manually.</description>
	</item>
	<item>
		<title>Bye, Bye EMBED</title>
		<link>http://tc.eserver.org/27931.html</link>
		<guid>http://tc.eserver.org/27931.html</guid>
		<description>Break the chains of EMBED and live free. Elizabeth Casto explains how to embed movies without using invalid markup.</description>
	</item>
	<item>
		<title>Rescue Terrible HTML with TagSoup</title>
		<link>http://tc.eserver.org/27749.html</link>
		<guid>http://tc.eserver.org/27749.html</guid>
		<description>XHTML is a friendly enough format for parsing and screen-scraping, but the Web still has a lot of messy HTML out there. In this tip Uche Ogbuji demonstrates the use of TagSoup to turn just about any HTML into neat XHTML.</description>
	</item>
	<item>
		<title>XHTML, HTTP accept-header and MIME-type application/xhtml+xml</title>
		<link>http://tc.eserver.org/27717.html</link>
		<guid>http://tc.eserver.org/27717.html</guid>
		<description>In 2005 it is high time to start serving XHTML as XML on a grand scale. Others have been doing it for years. I have been doing it since Christmas. Switching between XHTML as xml and text/html is easy using the HTTP accept header.</description>
	</item>
	<item>
		<title>Migrating from HTML to XHTML and XML - Part I</title>
		<link>http://tc.eserver.org/27673.html</link>
		<guid>http://tc.eserver.org/27673.html</guid>
		<description>This is the first part of a two-part article describing a detailed methodology for migrating HTML files to the structure and flexibility of XHTML and/or XML. By using XHTML to add structure and separate content from presentation, you&apos;ll be better positioned for a move to XML. Even if you never move to XML, your XHTML files will be easier to create and maintain, and will be more accessible.</description>
	</item>
	<item>
		<title>HTML, XHTML, Semantics and the Future of the Web</title>
		<link>http://tc.eserver.org/27636.html</link>
		<guid>http://tc.eserver.org/27636.html</guid>
		<description>Clarifies exactly what XHTML is, explains why you need to be learning about it from today, and steps through the process of transitioning to the standards based way of marking up for the web, and beyond.</description>
	</item>
	<item>
		<title>Migrating from HTML to XHTML and XML - Part II</title>
		<link>http://tc.eserver.org/27639.html</link>
		<guid>http://tc.eserver.org/27639.html</guid>
		<description>This is the second part of a two-part article describing a detailed methodology for migrating HTML files to the structure and flexibility of XHTML and/or XML.</description>
	</item>
	<item>
		<title>Fast and Easy XHTML</title>
		<link>http://tc.eserver.org/27511.html</link>
		<guid>http://tc.eserver.org/27511.html</guid>
		<description>Wondering how to turn your HTML markup into XHTML? Here are a few quick tips to teach you the very basics, a sample XHTML document, and resources for more information.</description>
	</item>
	<item>
		<title>Develop Wireless Applications with XHTML Mobile Profile</title>
		<link>http://tc.eserver.org/26880.html</link>
		<guid>http://tc.eserver.org/26880.html</guid>
		<description>The focus of most mobile technology applications developers is to build new wireless technologies that conform to varying bandwidth and memory limitations. With XHTML Mobile Profile, you can build apps that adhere to hardware requirements for users on different devices and render on multiple handheld devices.</description>
	</item>
	<item>
		<title>XHTML Web Design for Beginners</title>
		<link>http://tc.eserver.org/26650.html</link>
		<guid>http://tc.eserver.org/26650.html</guid>
		<description>Explores exactly what XHTML is, and how you can use it to start producing the next generation of Web pages.</description>
	</item>
	<item>
		<title>Extending XHTML: Target and Strict</title>
		<link>http://tc.eserver.org/25732.html</link>
		<guid>http://tc.eserver.org/25732.html</guid>
		<description>That the target attribute is not by default allowed in valid XHTML 1.1 or XHTML 1.0 Strict continues to be a source of frustration for designers. It simply doesn&apos;t have to be.</description>
	</item>
	<item>
		<title>XHTML by Example: A Hybrid Layout</title>
		<link>http://tc.eserver.org/25736.html</link>
		<guid>http://tc.eserver.org/25736.html</guid>
		<description>In this chapter, we’ll roll up our sleeves and apply what we’ve learned &#xD;about XHTML thus far to mark up a real-world design project. The &#xD;markup we create will be partly structural, partly transitional, and &#xD;fully standards-compliant.</description>
	</item>
	<item>
		<title>Linking in XHTML 2.0</title>
		<link>http://tc.eserver.org/25469.html</link>
		<guid>http://tc.eserver.org/25469.html</guid>
		<description>As a fundamental part of the Web, hypertext linking has been the subject of repeated attempts at standardization beyond the basic format allowed in simple HTML. Such attempts can be characterized as efforts to balance machine processing ability with authoring convenience. The latest specification in this area, XHTML 2.0, just might have gotten it right.</description>
	</item>
	<item>
		<title>Dynamic Text Replacement</title>
		<link>http://tc.eserver.org/23322.html</link>
		<guid>http://tc.eserver.org/23322.html</guid>
		<description>Let your server do the walking! Whether you&apos;re replacing one headline or a thousand, Stewart Rosenberger&apos;s Dynamic Text Replacement automatically swaps XHTML text with an image of that text, consistently displayed in any font you own. The markup is clean, semantic, and accessible. No CSS hacks are required, and you needn&apos;t open Photoshop or any other image editor. Read about it today; use it on personal and commercial web projects tomorrow.</description>
	</item>
	<item>
		<title>Joe Clark&apos;s Answers -- in Valid XHTML</title>
		<link>http://tc.eserver.org/23173.html</link>
		<guid>http://tc.eserver.org/23173.html</guid>
		<description>An extremely interesting but rather long read -- answers each question thoroughly and, there is plenty of discourse following the piece itself.</description>
	</item>
	<item>
		<title>XHTML Accessibility Tips</title>
		<link>http://tc.eserver.org/23126.html</link>
		<guid>http://tc.eserver.org/23126.html</guid>
		<description>The library is committed to serving the entire public, and that means striving to ensure that all pages of our site are accessible to the greatest possible number of people and devices (including audio browsers, Braille readers, and other specialized browsing environments).</description>
	</item>
	<item>
		<title>Introduction to XHTML</title>
		<link>http://tc.eserver.org/22645.html</link>
		<guid>http://tc.eserver.org/22645.html</guid>
		<description>Most people have heard of HTML - the language of the web. Far fewer have heard of XHTML. Believe it or not, HTML is dead and XHTML is here to take its place. This article goes through XHTML in technical detail, and points out the key differences between it and traditional HTML.</description>
	</item>
	<item>
		<title>XHTML: The Clean Code Solution</title>
		<link>http://tc.eserver.org/22650.html</link>
		<guid>http://tc.eserver.org/22650.html</guid>
		<description>XML continues to be a hot topic among web developers. Why? Because it delivers a standardized markup that separates display and layout code from syntax, making the creation, maintenance, and parsing of documents much easier for all involved.</description>
	</item>
	<item>
		<title>The Extensible HyperText Markup Language (XHTML) Tutorial</title>
		<link>http://tc.eserver.org/22334.html</link>
		<guid>http://tc.eserver.org/22334.html</guid>
		<description>The Extensible HyperText Markup Language (XHTML) is intended to be a replacement for HTML. XHTML has a stricter syntax than HTML and is the official recommendation. of the W3C. XHTML was required due to the poor standard of some HTML documents due to the forgiving nature of browsers. This tutorial discusses the issues in making your documents XHTML compliant.</description>
	</item>
	<item>
		<title>XHTML</title>
		<link>http://tc.eserver.org/21578.html</link>
		<guid>http://tc.eserver.org/21578.html</guid>
		<description>A collection of more than fifty online resources in the XHTML markup language.</description>
	</item>
	<item>
		<title>Streamlining with Web Standards</title>
		<link>http://tc.eserver.org/21172.html</link>
		<guid>http://tc.eserver.org/21172.html</guid>
		<description>Save time, money, blood, sweat, and tears by rebuilding your old-school site with standards-friendly CSS and XHTML.</description>
	</item>
	<item>
		<title>Transitional Layouts in (X)HTML and CSS: An Interview with Eric A. Meyer</title>
		<link>http://tc.eserver.org/20677.html</link>
		<guid>http://tc.eserver.org/20677.html</guid>
		<description>In a pivotal user test a couple years ago we found out one of the secrets of great web sites: they inspire confidence in users. This article explores how to measure it and use it to your advantage.</description>
	</item>
	<item>
		<title>Differences Between XHTML and HTML</title>
		<link>http://tc.eserver.org/20514.html</link>
		<guid>http://tc.eserver.org/20514.html</guid>
		<description>XHTML is the next generation of HTML, but it will of course take some time before browsers and other software products are ready for it.&#xD;&#xD;In the meantime there are some important things you can do to prepare yourself for it. As you will learn from this tutorial, XHTML is not very different from HTML 4.01, so bringing your code up to 4.01 standards is a very good start. Our complete HTML 4.01 reference can help you with that.&#xD;&#xD;In addition, you should start NOW to write your HTML code in lowercase letters, and NEVER make the bad habit of skipping end tags like the &lt;/p&gt;.</description>
	</item>
	<item>
		<title>XHTML 1.0 Reference</title>
		<link>http://tc.eserver.org/20513.html</link>
		<guid>http://tc.eserver.org/20513.html</guid>
		<description>A collection of the valid tags and attributes within XHTML &apos;strict&apos; encoding, with examples.</description>
	</item>
	<item>
		<title>XHTML Tutorial</title>
		<link>http://tc.eserver.org/20512.html</link>
		<guid>http://tc.eserver.org/20512.html</guid>
		<description>In this tutorial you will learn the difference between HTML and XHTML. You will also learn how this Web site was converted to XHTML.</description>
	</item>
	<item>
		<title> Migrating from HTML to XML</title>
		<link>http://tc.eserver.org/20458.html</link>
		<guid>http://tc.eserver.org/20458.html</guid>
		<description>As the Internet world shifts its focus to XML and related technologies, what happens to HTML? Everywhere you go, products are becoming &apos;XMLitized&apos; as vendors rush to gain market share. While this is great for companies that are only now beginning to build their infrastructures, what about the rest of us whose sites have existed for years, accumulating documents architected on old HTML technology? How are we to take our millions and millions of HTML documents and bring them into the next generation of Internet computing? Fortunately, the market for tools in this space is growing, and technologies like Extensible Hypertext Markup Language (XHTML) are making it easier to migrate your repository of existing HTML documents.</description>
	</item>
	<item>
		<title>NYPL Online Style Guide</title>
		<link>http://tc.eserver.org/20459.html</link>
		<guid>http://tc.eserver.org/20459.html</guid>
		<description>XHTML is the standard markup language for web documents and the successor to HTML 4. Library projects must be authored in structural XHTML 1.0 Transitional.&#xD;&#xD;The following topics provide all the information you need to create well-formed XHTML pages that validate and are accessible, and/or to convert old HTML pages to valid, well-formed, accessible XHTML.</description>
	</item>
	<item>
		<title>Web Developer Foundations: Using XHTML</title>
		<link>http://tc.eserver.org/20461.html</link>
		<guid>http://tc.eserver.org/20461.html</guid>
		<description>Web Developer Foundations provides an introduction to the skills and concepts that web developers need to know. The resources at this site are intended to aid you as you work through a related textbook.</description>
	</item>
	<item>
		<title>XHTML Design Guide</title>
		<link>http://tc.eserver.org/20462.html</link>
		<guid>http://tc.eserver.org/20462.html</guid>
		<description>This guide was created to help out all those who want to learn more about programming and designing scalable, modular and easy to maintain websites. HTML is hard enough! This eases the seasoned HTML programmer into fluent XHTML</description>
	</item>
	<item>
		<title>Marking Up Documents in XHTML</title>
		<link>http://tc.eserver.org/20392.html</link>
		<guid>http://tc.eserver.org/20392.html</guid>
		<description>XHTML is HTML described as an application of XML. It is very similar to HTML, indeed all the element names and their semantics are identical, but it has some important differences. We will look at the more important of these now.</description>
	</item>
	<item>
		<title>MarkUp Validation Service</title>
		<link>http://tc.eserver.org/20394.html</link>
		<guid>http://tc.eserver.org/20394.html</guid>
		<description>A free service that checks documents like HTML and XHTML for conformance to W3C Recommendations and other standards.</description>
	</item>
	<item>
		<title>XHTML 1.0: Marking Up a New Dawn</title>
		<link>http://tc.eserver.org/20393.html</link>
		<guid>http://tc.eserver.org/20393.html</guid>
		<description>Still writing your documents in HTML? If you are, you&apos;re not complying with current standards. On January 26, 2000, XHTML 1.0 became a recommendation by the World Wide Web Consortium (W3C). HTML, according to the W3C, is no longer the Web markup standard. Instead, XHTML 1.0 has replaced our old favorite, marking up the dawn of a new and exciting time in communications technology.</description>
	</item>
	<item>
		<title>Rated XHTML</title>
		<link>http://tc.eserver.org/20263.html</link>
		<guid>http://tc.eserver.org/20263.html</guid>
		<description>The W3C’s XHTML language is intended to bridge the web’s past (HTML) and future (XML). Shall we cross this bridge, now that we’ve come to it? Or is XHTML more trouble than it’s worth? Peter-Paul Koch puts forth the pros and cons.</description>
	</item>
	<item>
		<title>Better Living Through XHTML</title>
		<link>http://tc.eserver.org/20224.html</link>
		<guid>http://tc.eserver.org/20224.html</guid>
		<description>Everything you wanted to know about converting from HTML to XHTML, including why you’d want to, tools that help, changes in the way browsers display XHTML pages, shortcuts, bugs, workarounds, and other tips you won’t find elsewhere.</description>
	</item>
	<item>
		<title>Using XHTML/CSS for an Effective Search Engine Optimization Campaign</title>
		<link>http://tc.eserver.org/19632.html</link>
		<guid>http://tc.eserver.org/19632.html</guid>
		<description>We’re going to be focusing entirely on the benefits of using XHTML and CSS to show you how to improve the readability of your code for search engine spiders, maintain a good content-to-code ratio without going beyond file-size and word-count limits, and how to use CSS to mimic common image effects.</description>
	</item>
	<item>
		<title>Introducing XHTML</title>
		<link>http://tc.eserver.org/18755.html</link>
		<guid>http://tc.eserver.org/18755.html</guid>
		<description>The benefits of transforming HTML from a stand-alone language into an XML version of itself aren&apos;t immediately apparent until you understand the inherent value of XML. Since the language syntax is so strict in XML, parsers (the software that reads and understands the code you write) are a lot easier to develop. Ultimately, it will allow browsers to become smaller, faster, and more stable. It also means your code will behave in a far more predictable way: Either something will work, or you will get an error. It will be a marked difference from the voodoo we experience across multiple browsers today.</description>
	</item>
	<item>
		<title>Clean Up Your Act with XHTML</title>
		<link>http://tc.eserver.org/15100.html</link>
		<guid>http://tc.eserver.org/15100.html</guid>
		<description>Describes how elements and attributes are rendered in XHTML.</description>
	</item>
	<item>
		<title>XHTML: The Future of the Web</title>
		<link>http://tc.eserver.org/14613.html</link>
		<guid>http://tc.eserver.org/14613.html</guid>
		<description>Douglas McLaughlin describes the history and features of XHTML, a reformulation of HTML 4.0 using XML syntax.</description>
	</item>
	<item>
		<title>XHTML: What&apos;s in a Name(Space)?</title>
		<link>http://tc.eserver.org/14642.html</link>
		<guid>http://tc.eserver.org/14642.html</guid>
		<description>McLaughlin explains the use of namespaces in XHTML.</description>
	</item>
	<item>
		<title>No Standard for Migrating to Web Standards</title>
		<link>http://tc.eserver.org/14194.html</link>
		<guid>http://tc.eserver.org/14194.html</guid>
		<description>Lately, it seems like everyone is talking about migrating to web standards, like XHTML and Cascading Style Sheets (CSS). What&apos;s the big deal about these standards? Why should web teams invest the effort to learn new coding techniques and convert all their legacy sites over to standards-compliant sites? &#xD;&#xD;Time and Money, that&apos;s why.</description>
	</item>
	<item>
		<title>To Use or Not to Use: An XHTML Roadmap for Designers</title>
		<link>http://tc.eserver.org/13671.html</link>
		<guid>http://tc.eserver.org/13671.html</guid>
		<description>The problem with XHTML 1.0 isn&apos;t a matter of strength, or of importance. XHTML is both strong and important--and not just for markup snobs and hardcore developers. It&apos;s not that XHTML 1.0 has a particularly high learning curve. It doesn&apos;t--in fact, it&apos;s quite easy to learn. And, it&apos;s not that XHTML 1.0 doesn&apos;t display in browsers both current and past. When written with awareness of cross-browser considerations--just as with HTML, it does. The problem lies in the fact that XHTML is, quite simply, misunderstood.</description>
	</item>
	<item>
		<title>Modifying Dreamweaver to Produce Valid XHTML</title>
		<link>http://tc.eserver.org/13544.html</link>
		<guid>http://tc.eserver.org/13544.html</guid>
		<description>Dreamweaver 4 falls short in its ability to produce well-–formed, standards-–compliant markup. SOLUTION: You can easily harness Dreamweaver&apos;’s two greatest strengths, its flexibility and its user community, to make it one of the best tools on the market for producing good XHTML. This article will tell you how. With a few tweaks, hacks and extensions, you’ll be able to produce sites that validate, and to clean up legacy pages. Set aside an hour or two, follow these directions, and fall in love with Dreamweaver all over again.</description>
	</item>
	<item>
		<title>Fix Your Site With the Right DOCTYPE</title>
		<link>http://tc.eserver.org/13502.html</link>
		<guid>http://tc.eserver.org/13502.html</guid>
		<description>Per HTML and XHTML standards, a DOCTYPE (short for “document type declaration”) informs the validator which version of (X)HTML you’re using, and must appear at the very top of every web page. DOCTYPEs are a key component of compliant web pages: your markup and CSS won’t validate without them.</description>
	</item>
	<item>
		<title>&quot;Forgiving&quot; Browsers Considered Harmful</title>
		<link>http://tc.eserver.org/10207.html</link>
		<guid>http://tc.eserver.org/10207.html</guid>
		<description>Current browsers are very forgiving; they quietly correct or gloss over many common HTML errors. This makes it easy for people to experience the joy of creating their own web pages with a minimum of frustration—if a page displays correctly, then it&apos;s “right.” Unfortunately, by hiding the need for structure that the web will require as it moves towards XHTML and XML, these forgiving browsers have helped create a world of structural HTML illiterates. As long as browsers continue to parse and display HTML that isn&apos;t well-formed or valid, we will never learn the right ways, and we will never get to a structural web.</description>
	</item>
	<atom:link href="http://tc.eserver.org/dir/Design/Web-Design/XHTML.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>