Henning P. Schmiedehausen wrote:
- <shameless-plug mode="on">If your urge is pressing enough, consider making
a project from it and pay a consultant to implement it</shameless-plug>
I know a number of Apache people (me included) who got payed working on
Apache code and were allowed to put that back into the code base.
Unfortunately it's not too pressing, just annoying. Velocity has made
our site faster and easier to maintain which is great. It's just a shame
it's made the file sizes bigger, and considerably so (~10%). I'll
probably just create a whitespace gobbler filter of my own to stick on
the output. Should only take me a few minutes, will remove all nice
formatting, but will decrease the file size considerably.
But we *do* listen to you.
Good job. Third-party open source libraries are what is maintaining the
growth in the IT industry. We are very thankful of all the time and
effort you guys put in to projects like this.
If you need any more developers I'll be happy to contribute to such a
worthwhile project. I do have experience with parsers (antlr & JParse)
so I know what the problems and pitfalls of parsing are. But I think in
this case we only have to alter the parser in such a way as to treat
whitespace as an entity. Then, depending on the nesting of the
whitespace entity, depends on whether it appears in the output or is
discarded.
Of course this sounds easy but will depend heavily on the parser you're
using. I wouldn't mind taking a look though!
The best way for us to keep
track is opening an issue
(http://issues.apache.org/jira/browse/VELOCITY-253) and vote
there. :-)
Best regards
Henning
Maybe I should put this in there?
--
*Paul Loy
Software Developer*
Peoples Archive Ltd.
Middlesex House
34-42 Cleveland Street
London, W1T 4LB
Tel: +44 (0) 20 7323 0323
Fax: +44 (0) 20 7580 1938
[EMAIL PROTECTED]
www.peoplesarchive.com
This email has been scanned by Postini.
For more information please visit http://www.postini.com
