Complete.Org: Mailing Lists: Archives: freeciv-dev: December 2002:
[Freeciv-Dev] Re: (PR#2333) Add function die()
Home

[Freeciv-Dev] Re: (PR#2333) Add function die()

[Top] [All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index] [Thread Index]
Cc: freeciv-dev@xxxxxxxxxxx
Subject: [Freeciv-Dev] Re: (PR#2333) Add function die()
From: "Raimar Falke via RT" <rt@xxxxxxxxxxxxxx>
Date: Mon, 9 Dec 2002 01:03:25 -0800
Reply-to: rt@xxxxxxxxxxxxxx

On Sun, Dec 08, 2002 at 11:29:11PM -0800, Jason Short via RT wrote:
> 
> [rfalke - Sun Dec  8 10:33:07 2002]:
> 
> > An updated version is attached. I removed all cases which are
> > user-controlled. So a user shouldn't able to cause a die if he
> > supplied the wrong parameter, has a wrong installation or an invalid
> > ruleset. If however a program error occurs, or the user changed a
> > savegame the function will be called.
> 
> One question: what about translation?
> 
> Choices:
> 
> - Translate all messages.
> - Translate no message.
> - Translate some messages.
> 
> Currently #3 is used, but IMO the way this is done is arbitrary.  I
> think either #1 or #2 is acceptable.

I'm for #2.

> One thing we could do is make die() auto-translate, just like _().
> This is easier than #1, but is a hack.

Won't work since you need to mark the strings with N_(). But if you do
this you can also translate them with _().

        Raimar

-- 
 email: rf13@xxxxxxxxxxxxxxxxx
  "The primary purpose of the DATA statement is to give names to
   constants; instead of referring to pi as 3.141592653589793 at every
   appearance, the variable PI can be given that value with a DATA
   statement and used instead of the longer form of the constant. This
   also simplifies modifying the program, should the value of pi
   change."
    -- FORTRAN manual for Xerox Computers




[Prev in Thread] Current Thread [Next in Thread]