Christoph Reck said: > Nathan Bubna wrote: > > Christoph Reck said: > > > >>having a completely whitespace-gobbling-free handling is a clean as > >>you can get; but it is not what most people expect. > > > > > > hard to say, i've taken no polls. personally, i expect WYTIWYG > > from a template language. :) but still... > > I expect that when adding velocity markup to an existing text file > to not affect the spacing in the output. This includes indented #foreach > directives and inner indented #if/#set/#macro directives. > I have seen others on the list also complaining about the extra > whitespaces emitted in such cases.
i don't think everyone will always agree on what whitespaces are "extra." i understand your proposed gobbling rules, and i think they're quite useful. i really don't think we're very far apart here. i'm merely saying that plain vanilla velocity (default) shouldn't gobble, but i'd like to be able to configure it with relative ease to gobble according to your rules or any other rules of choice. saying much more than that (implementation details) is uncomfortable for me because i haven't really looked into the necessary code or thought it through. i'm only saying how i think it ought to work, not how best to make it work that way. ... > Please note that I'm differentiating between reformatting the AST at > parse time (e.g. gobbling nodes with whitespaces...) and filtering the > output after a merge. i don't think any of us are talking about filtering the output *after* a merge. we don't need to change velocity at all to do that. Nathan Bubna [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
