> From: Jon Scott Stevens [mailto:[EMAIL PROTECTED]] > > on 6/9/02 1:46 PM, "Jeff Schnitzer" <[EMAIL PROTECTED]> wrote: > > > I suspect the Turbine people will want this for the same reason I do - > > in order to do Screen/Layout processing (or in Maverick, a document aka > > wrapping transform), the output of the "inner" page is passed to the > > "outer" layout page as a String in the context. That string will of > > course contain html which must not be escaped. > > T3 no longer does this.
Really? Then how does it handle layout-type processing? I checked the docs, but they haven't been written yet :-) Yes, I checked the source too, but it's not obvious. Ok, maybe this is a little off-topic, but it helps justify my claim (which I don't think is all that controversial) that with output escaping enabled, it is still necessary for Velocity to be able to insert unmolested XML strings. A simple filter on the writer does not accommodate this need. (Yes, I know a de-escaping tool would work, but this is ugly and expensive compared to simply not having escaped in the first place). Jeff Schnitzer [EMAIL PROTECTED] -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
