> In general, I like the structure of the .printer code more than what is > currently in Xalan, and think it would be a great starting base.
Scott, thank you. The exisiting code base deals with CData (setCDataElements) and raw characters (setUnescapedElements). There are also event handles for comments and entity reference but these only work for DOM right now. No problem adding a DocumentHandlerEx to make them available for SAX. The design was based on the latest XSLT draft, so XSLT requirements have been taken care of ;-) There's need for the printers to be available for XML parser users. The printers in Xalan required a separate download, are very well hidden (took me two attempts to locate them because I knew they were there!), and have an XSL-oriented API. I totally agree we need a separate tree walker. In my opinion there should be a set of generic utility classes, including DOM->SAX, SAX->DOM, whitespace handling, namespace stripping, etc. My personal opinion is that the basic printers belong in the parser, the parser being the more general case of XML usage. I assume most users who download Xalan also have Xerces installed, or can obtain the printer/utility packages separately. In my understanding FOP implements it's own printer that requires the FOP code base, and Cocoon should implement it's own framework for printers to use the default, FOP or whatever comes along (application code). arkin > > -scott -- ____________________________________________________________ Assaf Arkin [EMAIL PROTECTED] CTO http://www.exoffice.com Exoffice, The ExoLab Company tel: (650) 259-9796
