I've got this working now locally, with a set of tests, as well.
I've applied Daniel's patch to my local copy of the code, though, so
if I do a svn diff,
the resulting patch is going to include both his stuff and mine;
would that be preferable, or shall I wait
until his patch is applied to svn to do the diff?
Robert
On Mar 14, 2007, at 3/143:35 PM , Robert Zeigler 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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
