Joshua Levy <[EMAIL PROTECTED]> writes:
> Thanks very much for the first beta release of Velocity! It
> looks great. I don't know if this should go to velocity-user
> or velocity-dev, but here goes:
>
> The Apache on line bug db (http://nagoya.apache.org/bugzilla/enter_bug.cgi)
> doesn't know about Velocity, so you can't file bugs against it.
For now, please just send bugs to the dev or user mailing lists.
They're addresses immediately (rather than left to rot in Bugzilla,
heh).
> It would be nice to have the javadocs for Velocity available on line
> somewhere on the velocity web page. (Maybe they are, but I could not
> find them.)
Indeed it would. While we're making wishes, JXR would be great, too.
;P
I think these two things are mostly just waiting on volunteers with
free time, now.
> Many (all?) of the text files in the Velocity distribution are "UNIX
> style". They only have a newline character at the end of each line.
> This makes them hard to view on a PC. (I think the fix for this is
> just to add a carrage return to each line, as these will be ignored
> by vi and emacs. Or maybe the trick is to change the extension to
> ".asc", which will cause PCs to use WordPad as the viewer, instead of
> notepad, and WordPad does understand newline terminated lines.)
> The README file in the example directory, and the one in the
> context_example directory both have this problem.
I use a PC every day. It runs Linux.
When circumstances force me to use another OS on a PC, I generally
install a real text editor to deal with insignificant platform issues
like line endings. May I suggest XEmacs <http://xemacs.org/>?
Under MS Windows, I generally add said editor to the "Send to program"
list, so I can right click on the file I'd like to browse and open it
in the non-toy editor.
If I remeber correctly, the editor built into the MS Visual Studio IDE
handles such issues just fine.
Daniel Rall
