XHTML is the standardisation of HTML into a XML document. XHTML is an attempt to bring standards to the web by formalising the structure of HTML.

There is nothing specifically in XHTML that can generate email messages from form content. Markup only specifies how the form will be structured, the fields it has and what to do when it is submitted. You will need a server side script to format the submission as email and send it via an email server.

There are no killer reasons to switch to using XHTML instead of HTML at this time. Indeed it would lower accessibility of APLAWS since browser support for XHTML is considerably worse than that for traditional HTML. An article on http://www.alistapart.com/articles/xhtml, A List Apart provides more information. If after reading this, you did still want to generate XHTML, it would be a simple matter to change the xsl:output tags in the XSL templates used for presenting APLAWS:

Yes. You must pass form_parser_class=ClientForm.XHTMLCompatibleFormParser to ParseResponse() / ParseFile(). Note this parser is less tolerant of bad HTML than the default, ClientForm.FormParser

XHTML+Voice, or X+V for short, is a mark-up language for multimodal Web pages. With X+V, Web developers can create Web pages that let end users use voice input and output as well as traditional visual (GUI) interaction. X+V does this by providing a simple way to add voice mark-up to XHTML; hence the name "XHTML plus Voice." X+V fits into the Web environment by taking a normal visual Web user interface and speech-enabling each part of it.

XHTML is the keystone in W3C?s effort to create standards that provide richer web sites on an ever-increasing range of browser platforms. Browsers are not limited to desktops, instead there are platforms including mobile devices, televisions, cars and wireless personal digital assistants (PDA). Using XHTML, content providers will find it easier to produce content for a wide range of platforms, with better assurances as to how the content is rendered.

XHTML Basic is the mobile version of XHTML 1.1. XHTML Basic is designed for Web clients that do not support the full set of XHTML features; for example, Web clients such as mobile devices, PDAs, pagers and set-top boxes. With XHTML Basic, a document can be presented on the maximum number of web clients, including a wide range of mobile devices featuring different display formats and presentation capabilities.

XHTML Doclet is an alternative doclet for Javadoc. In a nutshell, it creates ouptut that is compliant with web standards and structured to allow for flexible styling, which offers enhanced control over output appearance. Javadoc itself handles the first stage: parsing the source code and creating a representative data structure. It sends that data to a doclet, which must include a method void start(RootDoc), as described on the Doclet Overview page.

Extensible HyperText Markup Language reproduces, subsets, and extends HTML, reformulated as an XML application. XHTML 1.0 is identical to HTML 4.01, except for the syntax requirements imposed by XML. XHTML Basic is a minimal subset of XHTML for Web clients with limited capabilities. XHTML 1.1 is a reformulation of XHTML 1.0 Strict using XHTML Modules.

The simplest way to refresh a page on a regular basis is to use an HTML meta element like this: <meta http-equiv="Refresh" content="10; URL=http://yoursite.example/Refresher.html" /> The short answer is yes, you can adapt the XHTML DTD to create your own document structures. This works best where you are enforcing more strict rules on your documents, like making the width and height attributes of images compulsory for instance.

Web browsers are mainly used for accessing Internet URLs, so there is not a common standard for referring to documents on the local file system. Try opening files with a number of target Web browsers and check for variations in the reference scheme in the address bar.