#20224
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.
Zeldman, Jeffrey. List Apart, A (2002). Design>Web Design>XHTML
#27931
Break the chains of EMBED and live free. Elizabeth Casto explains how to embed movies without using invalid markup.
Castro, Elizabeth. List Apart, A (2006). Design>Web Design>Multimedia>XHTML
#15100
Describes how elements and attributes are rendered in XHTML.
McLaughlin, Douglas J. Intercom (2000). Design>Web Design>XHTML
#26880
Develop Wireless Applications with XHTML Mobile Profile 
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.
Saleeb, Hany. IBM (2006). Articles>Web Design>Wireless Web>XHTML
#20514
Differences Between XHTML and HTML
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. 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. 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
.#29329
Download our Site Template and Make the Leap to XHTML and CSS2 
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.
Morton, Shawn. TechRepublic (2003). Design>Web Design>Standards>XHTML
#23322
Let your server do the walking! Whether you're replacing one headline or a thousand, Stewart Rosenberger'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't open Photoshop or any other image editor. Read about it today; use it on personal and commercial web projects tomorrow.
Rosenberger, Stewart. List Apart, A (2004). Design>Web Design>CSS>XHTML
#25732
Extending XHTML: Target and Strict
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't have to be.
Burkett, Wayne. Dionidium (2004). Design>Web Design>Standards>XHTML
#22334
The Extensible HyperText Markup Language (XHTML) Tutorial 
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.
Lemon, Gez. Juicy Studio (2009). Design>Web Design>XHTML
#27511
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.
Kaiser, Shirley E. Website Tips (2001). Design>Web Design>HTML>XHTML
#13502
Fix Your Site With the Right DOCTYPE
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.
Zeldman, Jeffrey. List Apart, A (2002). Design>Web Design>Standards>XHTML
#10207
"Forgiving" Browsers Considered Harmful
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'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't well-formed or valid, we will never learn the right ways, and we will never get to a structural web.
Eisenberg, J. David. List Apart, A (2001). Design>Web Design>Standards>XHTML
#27636
HTML, XHTML, Semantics and the Future of the Web
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.
Allsopp, John. Western Civilization (2005). Articles>Web Design>Information Design>XHTML
#18755
The benefits of transforming HTML from a stand-alone language into an XML version of itself aren'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.
Veen, Jeffrey. Webmonkey (1999). Design>Web Design>Standards>XHTML
#22645
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.
Duffy, Scott. XGuru (2003). Design>Web Design>XHTML
#23173
Joe Clark's Answers -- in Valid XHTML
An extremely interesting but rather long read -- answers each question thoroughly and, there is plenty of discourse following the piece itself.
Clark, Joe. Slashdot (2002). Articles>Web Design>Accessibility>XHTML
#25469
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.
Dubinko, Micah. IBM (2005). Articles>Web Design>Standards>XHTML
#28240
IE/Win does not render these quotation marks, and because of this, most web authors choose not to use the Q tag. I'm here to change all that!
Cordoni, Stacey. List Apart, A (2006). Design>Web Design>HTML>XHTML
#20392
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.
#20394
A free service that checks documents like HTML and XHTML for conformance to W3C Recommendations and other standards.
#27673
Migrating from HTML to XHTML and XML - Part I
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'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.
James-Tanny, Char. WritersUA (2006). Design>Web Design>Standards>XHTML
#27639
Migrating from HTML to XHTML and XML - Part II
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.
James-Tanny, Char. WritersUA (2006). Articles>Web Design>Standards>XHTML
#20458
As the Internet world shifts its focus to XML and related technologies, what happens to HTML? Everywhere you go, products are becoming 'XMLitized' 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.
Fischer, Peter. New Architect (2000). Design>Web Design>XML>XHTML
#13544
Modifying Dreamweaver to Produce Valid XHTML
Dreamweaver 4 falls short in its ability to produce well-–formed, standards-–compliant markup. SOLUTION: You can easily harness Dreamweaver'’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.
Bickner, Carrie. List Apart, A (2002). Design>Web Design>XHTML>Dreamweaver
#14194
No Standard for Migrating to Web Standards
Lately, it seems like everyone is talking about migrating to web standards, like XHTML and Cascading Style Sheets (CSS). What'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? Time and Money, that's why.
Porter, Joshua. User Interface Engineering (2002). Design>Web Design>Standards>XHTML
