RE: What should `svn commit' print?

I'd prefer the "easily read message" approach as well. (i.e. localizable
words)
The commit messages can only be output after the commit actually
succeeds anyway.

The reason for doing it this way would be to reduce end user confusion
if the transaction aborts, after printing that something had gotten done
that actually hadn't.

WinSVN will certainly be localizable. The current prototype relies on
Win32 String Tables for that purpose.
It would certainly be feasible to use the gettext solution for the
status messages that the client uses.

Bill

From: Branko Cibej [mailto:brane@xbc.nu]
> Greg Stein wrote:

> > Personally, I'm not bothered by the full words. Why the need to be
terse?
> > We're down to a single line, which is the important part. No need to
be
> > horizontally-terse :-) Single letters vs words are the same
complexity to
> > parse, yet the word is easier for the human.

> This is far out, but ... whole words (should/will/have to) be
> localizable. I know we haven't thought about i18n and l10n much yet,
but
> maybe it's not a bad time to start.

> IIRC we /did/ talk about having a verbosity switch, so maybe we should
> use single characters (non-localizable) by default, and whole words
> (localizable) at a higher verbosity level. And not just for commit, of
> course.
Received on Sat Oct 21 14:36:19 2006