Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@cygnus.com>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: gdb@sources.redhat.com
Subject: Re: how to format an error?
Date: Sat, 02 Feb 2002 08:09:00 -0000	[thread overview]
Message-ID: <3C5C0F2B.2050409@cygnus.com> (raw)
In-Reply-To: <Pine.SUN.3.91.1020114102101.14027J-100000@is>

> On Sun, 13 Jan 2002, Andrew Cagney wrote:
> 
> 
>> Given the attached, which is the correct way of formatting an error message:
>> 
>> This is an error message.
>> this is an error message.
>> This is an error message
>> this is an error message
> 
> 
> I suggest the last variant.  It goes with the GNU coding standards
> except for the capitalization.  But capitalization is
> language-specific (e.g., in German, all nouns are capitalized), and it
> was recently discovered in Emacs development that a 100% adherence to
> the capitalization rule you cited produces wrong results in some
> cases.  Most of the messages don't need caps, so I think losing that
> is the best alternative which is simple enough to adher to.


Wouldn't the gettext stuff let the german translator do this?  The 
translator certainly isn't required to follow the capitalization 
convention used in the Australian English version.

Anyway, we agree on one thing - the trailing fullstop.  I'll ARI that :-)

Andrew

http://www.gnu.org/prep/standards_15.html#SEC15
http://www.gnu.org/prep/standards_30.html#SEC30



  parent reply	other threads:[~2002-02-02 16:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-13 20:36 Andrew Cagney
2002-01-14  0:22 ` Eli Zaretskii
2002-01-14  2:37   ` Richard Earnshaw
2002-01-14  3:08     ` Eli Zaretskii
2002-02-02  8:09   ` Andrew Cagney [this message]
2002-02-02  9:27     ` Eli Zaretskii
2002-02-03 19:22       ` Andrew Cagney

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3C5C0F2B.2050409@cygnus.com \
    --to=ac131313@cygnus.com \
    --cc=eliz@is.elta.co.il \
    --cc=gdb@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox