Complete.Org: Mailing Lists: Archives: freeciv-dev: January 2003:
[Freeciv-Dev] Re: (PR#1824) Re: Re: (PR#2743) Blank messages and bad pac
Home

[Freeciv-Dev] Re: (PR#1824) Re: Re: (PR#2743) Blank messages and bad pac

[Top] [All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index] [Thread Index]
To: jdorje@xxxxxxxxxxxxxxxxxxxxx, jrg45@xxxxxxxxxxxxxxxxx, Kenn.Munro@xxxxxxxxxxxxxx
Cc: freeciv-dev@xxxxxxxxxxx
Subject: [Freeciv-Dev] Re: (PR#1824) Re: Re: (PR#2743) Blank messages and bad packet strings
From: "Raimar Falke via RT" <rt@xxxxxxxxxxxxxx>
Date: Fri, 10 Jan 2003 01:14:27 -0800
Reply-to: rt@xxxxxxxxxxxxxx

On Thu, Jan 09, 2003 at 11:17:02PM -0800, Jason Short via RT wrote:
> Raimar Falke wrote:
> 
> > I disagree if this means that the city name "Köln" won't be longer
> > allowed. Unicode with one of its encodings would be best?! The only
> > problem is IMHO that this makes another dependency?!
> 
> I agree the accented characters are nice.  But if you allow latin1 
> characters why not latin2 characters?  Why not allow Japanese 
> characters?  Where do you draw the line?
> 
> But, I agree with you.  We should allow the ruleset to specify its 
> encoding, and have freeciv convert from that encoding to the local 
> encoding when loading it.  Where to draw the line is a data issue, and 
> it's always possible for modpack authors to set their own standards.
> 
> A good start would be to convert from latin1 into the local encoding 
> when loading the ruleset.  That fixes PR#752/1824/2445/2743.  (I assume 
> iconv can do something intelligent when converting an accented character 
> into an ascii encoding.)
> 
> For anyone interested in this issue, if you haven't been following it 
> from the start you may want to re-read PR#1824 from the beginning. 
> There's a lot of talk and no real solutions...

I ask another time: Is unicode the best solution? Why don't we use it?

        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]