Ideally, it would all be driven by the encoding specified by the xml template. As a second choice, I think it should be driven by a configurable symbol.
No, neither of both makes sense here. The only thing that is required to fix the bug is that reading uses the same encoding as writing. This is just internal processing of the content and only the doctype of the document is accessed here. It hat neither to do with the encoding that is used for reading the xml document nor with the encoding of the resulting (x)html file.
This is a trivial bugfix and the discussion here already took more time to fix it (using the fix+testcase I provided in TAP5-2219).
Kind regards, Michael. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org For additional commands, e-mail: dev-h...@tapestry.apache.org
