Our template uses the following DOCTYPE definition:
<!DOCTYPE html
PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd";>What's wrong with this to get well-formed XML? Thx && cheers, Martin On Mon, 2007-06-18 at 10:29 -0700, Howard Lewis Ship wrote: > To elaborate; Tapestry uses the <!DOCTYPE> of the component template > to determine the type of markup it will send; when the !DOCTYPE is > omitted, it is assumed to be legacy HTML as defined by SGML, where > many element are unclosed. When you provide an explicit !DOCTYPE, > Tapestry switches over to rendering out well-formed XML. > > On 6/18/07, Robin Ericsson <[EMAIL PROTECTED]> wrote: > > On 6/18/07, Martin Grotzke <[EMAIL PROTECTED]> wrote: > > > Hi, > > > > > > T5 currently renders markup that is not XHTML compliant. > > > > Yes and no. > > > > > E.g. the element '<meta http-equiv="Content-Type" content="text/html; > > > charset=utf-8" />' is rendered as '<meta content="text/html; > > > charset=utf-8" http-equiv="Content-Type">' - the tag is not closed > > > properly. > > > > > > Is there any way to force T5 to generate XHTML compliant markup? > > > > If your template uses HTML (SGML) markup, T5 generates HTML markup, if > > your template uses XHTML, T5 generates XHTML. See previous posts on > > this list. > > > > -- > > regards, > > Robin > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > -- Martin Grotzke http://www.javakaffee.de/blog/
signature.asc
Description: This is a digitally signed message part
