:-) By DTD pass-through, do you mean having the first template DOCTYPE encountered output into the final HTML? If so, how's that going?
On 3/15/07, Robert Zeigler <[EMAIL PROTECTED]> wrote:
Scratch that... getting late. I've been working on adding DTD pass- through... I have an extra token in my branch for the DTD. :) Robert On Mar 14, 2007, at 3/1411:44 PM , Robert Zeigler wrote: > Interestingly (line-ending issue?), the "doctype_parsed_correctly" > tests failed on my machine. > 11 tokens instead of 10; <Test> was the 8th token instead of the > 7th. Playing with that now. > > Robert > > On Mar 14, 2007, at 3/1411:01 PM , D&J Gredler wrote: > >> I've taken a pass at the packaged DTDs: >> >> https://issues.apache.org/jira/browse/TAPESTRY-1353 >> >> >> On 3/14/07, D&J Gredler <[EMAIL PROTECTED]> wrote: >>> >>> Might be cool, might not... now's the time to try, though, while >>> things >>> are still in flux :-) >>> >>> Either way, providing packaged DTDs would be nice... you >>> basically can't >>> develop offline as things stand right now. >>> >>> >>> On 3/14/07, Howard Lewis Ship <[EMAIL PROTECTED]> wrote: >>> > >>> > I've been thinking of packaging common XHTML DTDs with the JARs to >>> > prevent unnecessary nettwork access. Perhaps we could >>> substitute an >>> > XML version of the HTML SGML DTD? >>> > >>> > On 3/14/07, Robert Zeigler < [EMAIL PROTECTED]> wrote: >>> > > Sounds reasonable, including first wins. >>> > > >>> > > What about the fact that the SAX parser chokes on the html >>> > > transitional & strict dtd's due to the sgml-style comments >>> within >>> > > element definitions? >>> > > >>> > > Robert >>> > > >>> > > On Mar 14, 2007, at 3/1411:37 AM , Howard Lewis Ship wrote: >>> > > >>> > > > I can see this as a new type of token that propogates up. >>> > > > >>> > > > Using LexicalHandler.startDTD(), we can know if a template >>> has a <! >>> > > > DOCTYPE>. >>> > > > We could record this data in a special token, and make >>> some changes >>> > > > to the MarkupWriter and Document classes to accomidate the >>> token. >>> > > > >>> > > > The problem is: any and every template for a page may >>> contain a >>> > > > DOCTYPE. How do we know which to use? What if there's a >>> conflict? >>> > > > >>> > > > I guess it'll be "first wins". So if the page template has a >>> > doctype, >>> > > > that will be explicit. In a typical application with a Layout >>> > > > component (aka a "Border"), the Layout will likely contain a >>> > > > <!DOCTYPE> (along with <html>, etc.). >>> > > > >>> > > > >>> > > > On 3/14/07, Robert Zeigler <[EMAIL PROTECTED]> wrote: >>> > > >> Howard, >>> > > >> >>> > > >> What are your thoughts on how to get doctypes from >>> templates into >>> > the >>> > > >> rendered output stream? Put another way, what's preventing >>> this >>> > from >>> > > >> happening at the moment? This is something I'm needing at the >>> > moment, >>> > > >> so I'd be happy to jump in and and take care of this todo... >>> > > >> >>> > > >> Robert >>> > > >> >>> > > >> >>> > >>> -------------------------------------------------------------------- >>> - >>> > > >> 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 >>> > > > >>> > > > >>> > >>> -------------------------------------------------------------------- >>> - >>> > > > To unsubscribe, e-mail: [EMAIL PROTECTED] >>> > > > For additional commands, e-mail: [EMAIL PROTECTED] >>> > > >>> > > >>> > > >>> -------------------------------------------------------------------- >>> - >>> > > 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 >>> > >>> > >>> -------------------------------------------------------------------- >>> - >>> > To unsubscribe, e-mail: [EMAIL PROTECTED] >>> > For additional commands, e-mail: [EMAIL PROTECTED] >>> > >>> > >>> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
