public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: kaih@khms.westfalen.de (Kai Henningsen)
To: gcc@gcc.gnu.org
Subject: Re: new parser: error recovery needs work
Date: Sun, 19 Jan 2003 14:38:00 -0000	[thread overview]
Message-ID: <8e5PWxRHw-B@khms.westfalen.de> (raw)
In-Reply-To: <3E284DF0.4020604@apple.com>

shebs@apple.com (Stan Shebs)  wrote on 17.01.03 in <3E284DF0.4020604@apple.com>:

> Neil Booth wrote:
>
> >Fergus Henderson wrote:-
> >
> >
> >>We've discussed this before.  The concensus last time (as I understood it)
> >>was that alphanumeric message codes where a better alternative to message
> >>numbers.  Message codes are easier to remember, more self-documenting,
> >>and avoid collisions between new warnings added on different CVS branches
> >>or in different repositories.
> >>
> >
> >I take it the idea is that the message code is similar to the text?
> >
> >Then how do we handle internationalization, where users in a different
> >language have never even seen, let alone understand, the English form of
> >the message?
> >
> My theory is to have the names be basically the same as what the
> -Wxxx options use now, so for -Wmissing-prototypes, "missing-prototypes"
> is the name of the warning, and would be available for attributes and
> pragmas just as for command-line options.  The names are orthogonal to
> localization, they're just arbitrary strings.
>
> Although perhaps to be more politically correct, we should borrow
> from various languages for names.  How about -Wabwesende-Urbilder? :-)

That might make German programmers look funny at you - I've never seen  
prototypes translated as "Urbilder". I think "Prototypen" is usually used,  
and not only with computers. "Urbilder" sounds like it might be used in  
psychology or philosophy. (In fact, Duden/Oxford only mentions  
"Prototyp".)

Of course, you'd also not translate "missing" with "abwesend" for similar  
though less drastic reasons - it's "fehlend". Which makes this "-Wfehlende- 
Prototypen" ...

Oh, and this points out a last problem, that replacing space with dash  
here *really* looks bad in German. Sorry, no better alternative comes to  
mind.

All in all, I'd prefer keeping those switches English. Translate the docs  
instead. After all, it's still "if" and not "wenn" in the language, as  
well!

MfG Kai

  reply	other threads:[~2003-01-19  5:09 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-16 13:40 Robert Dewar
2003-01-16 17:20 ` Joe Buck
2003-01-16 18:15   ` Mark Mitchell
2003-01-16 17:34 ` Joe Buck
2003-01-16 18:05   ` Gareth Pearce
2003-01-16 20:00     ` Phil Edwards
2003-01-16 20:15       ` Neil Booth
2003-01-16 21:43       ` Janis Johnson
2003-01-16 23:33         ` Mark Mitchell
2003-01-17  8:12         ` Fergus Henderson
2003-01-17 10:06           ` Stan Shebs
2003-01-17 11:36           ` Ben Elliston
2003-01-17 19:15             ` DJ Delorie
2003-01-17 12:27           ` Neil Booth
2003-01-17 23:26             ` Stan Shebs
2003-01-19 14:38               ` Kai Henningsen [this message]
2003-01-19  5:18             ` Fergus Henderson
2003-01-19  7:02               ` Neil Booth
2003-01-19  9:45                 ` Fergus Henderson
2003-01-19 11:38               ` Zack Weinberg
2003-01-18 16:46           ` Gabriel Dos Reis
2003-01-17  8:12         ` Phil Edwards
2003-01-18 16:48           ` Gabriel Dos Reis
2003-01-17  5:26       ` Gareth Pearce
2003-01-17  8:36         ` Phil Edwards
2003-01-17  9:10           ` Gareth Pearce
2003-01-18 16:32       ` Gabriel Dos Reis
2003-01-19 14:48         ` Kai Henningsen
2003-01-19 19:45         ` Phil Edwards
2003-01-16 23:04     ` Mark Mitchell
2003-01-18 16:52       ` Gabriel Dos Reis
  -- strict thread matches above, loose matches on Subject: below --
2003-01-19 17:31 Robert Dewar
2003-01-18 21:53 Robert Dewar
2003-01-14 14:31 Jeff Donner
2003-01-14  1:24 Joe Buck
2003-01-14  7:35 ` Mark Mitchell

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=8e5PWxRHw-B@khms.westfalen.de \
    --to=kaih@khms.westfalen.de \
    --cc=gcc@gcc.gnu.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).