[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Standard error message format
From: |
Ralf Wildenhues |
Subject: |
Re: Standard error message format |
Date: |
Fri, 28 Jan 2011 20:22:46 +0100 |
User-agent: |
Mutt/1.5.20 (2010-08-04) |
* Bruce Korb wrote on Fri, Jan 28, 2011 at 05:28:10PM CET:
> On 01/27/11 16:16, Karl Berry wrote:
> > (Although, switching topics a bit, I wonder if
> > users might like to have all such errors cast in the above format so
> > that next-error would do something sensible with them
>
> Makes sense for where it makes sense. :) WRT the program name,
> though, it ought to be mandatory. Or as mandatory as you can get,
> post-facto. Although, switching topics back a bit, if the
> program name introduces a full sentence, oughtn't it be properly
> capitalized?
> fumble: You just fumbled this.
No (and I think GCS also documents this): words for which
(non-)capitalization is relevant should not be (de-)capitalized;
you don't want to wonder whether GraphicsMagick-config or Xorg
really are spelt that way or not.
Cheers,
Ralf
- Re: sc_error_message_uppercase, (continued)
capitalization of error messages and option descriptions, Bruno Haible, 2011/01/27
- Re: capitalization of error messages and option descriptions, Simon Josefsson, 2011/01/27
- Re: capitalization of error messages and option descriptions, Jim Meyering, 2011/01/27
- Re: capitalization of error messages and option descriptions, Ralf Wildenhues, 2011/01/27
- Re: capitalization of error messages and option descriptions, Karl Berry, 2011/01/28
- Standard error message format (was Re: capitalization of error messages...), Bruce Korb, 2011/01/28
- Re: Standard error message format,
Ralf Wildenhues <=
- Re: Standard error message format, Bruce Korb, 2011/01/28
- Re: Standard error message format, Karl Berry, 2011/01/28
- Re: Standard error message format, Ralf Wildenhues, 2011/01/28