On Fri, 2007-06-29 at 11:57 -0700, Howard Lewis Ship wrote: > This is an unimplemented feature; currently Tapestry isn't smart > enough to output well-formed markup just because the template > specified an XML doctype. Please check JIRA and add an issue if not > present. Ok, I'll do this.
This issue is very crucial for us, so until this feature is implemented we need to implement some workaround or quick fix that creates valid xhtml output. What would be the best way to accomplish this? Alternatively we would like to help implementing this feature if it's somehow possible. Thanx && cheers, Martin > > On 6/19/07, Martin Grotzke <[EMAIL PROTECTED]> wrote: > > On Mon, 2007-06-18 at 20:21 +0200, Martin Grotzke wrote: > > > 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? > > Or is the doctype correct and s.th. else might be the reason > > for the not well-formed xml? > > > > Cheers, > > Martin > > > > > > > > > > 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/ > > > > > > -- Martin Grotzke http://www.javakaffee.de/blog/
signature.asc
Description: This is a digitally signed message part
