> Geir, what about this: Remove whitespace > gobbling from the "core", add pluggable preprocessor support, and then > pack two preprocessor classes with the Velocity releases: > > - CompatibilityPreprocessor: A preprocessor which gobbles whitespace > exactly like old velocity (I mean velocity 1.3 here) did. > > - SGMLPreprocessor: A preprocessor which gobbles whitespace based on > the method proposed by Christoph and me. This is for HTML/XML maker > users. > > and then let the CompatibilityPreprocessor by the default in the > org\apache\velocity\runtime\velocity.properties: > preprocessor.class = > org.apache.velocity.app.preprocessor.CompatibilityPreprocessor > > > Ideas? Votes? Come on! :)
"Immediate satisfaction" solution! +1 There is still the issue on how we decide which preprocessor to use though. The designer wants to set it in the template (?), the programmer doesn't care and the 'deployer' wants it application-specific. What if one can name a set of preprocessor in the config files, then the designer can switch easily between them with a directive: #set($format = "RAW") #set($format = "GobbleWhitespace") #set($format = "XMLFile") -- Denis. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
