Just hasn't been fleshed out yet; there needs to be a negotiation between the MarkupWriterFactory service and the page that does the rendering to determine the correct MarkupWriter configuration for the result.
On 5/29/07, Martin Dietze <[EMAIL PROTECTED]> wrote:
Hi, > Howard Lewis Ship wrote on Sat, 24 Mar 2007 11:42:22 -0800 > This is correct behavior for rendering HTML (as opposed to XHTML). > Unlike T4, T5 knows the difference. HTML is a SGML language where > open tags are not necessarly balanced with close tags. > What's coming is the ability for Tapestry to render XML/XHTML > correctly and choose the correct strategy (HTML vs. XML/XHTML) > automatically. does this imply that T5 will be able to do this one day or is there any way to enforce XHTML-compliant output with T5 as it is now? Cheers, Martin -- ------------- / http://herbert.the-little-red-haired-girl.org / ------------- =+= WE ARE THE BORG - RESISTANCE IS VOLTAGE DIVIDED BY CURRENT! --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Howard M. Lewis Ship TWD Consulting, Inc. Independent J2EE / Open-Source Java Consultant Creator and PMC Chair, Apache Tapestry Creator, Apache HiveMind Professional Tapestry training, mentoring, support and project work. http://howardlewisship.com
