The same applies as to my previous post...
Sorry again.
S.
----- Original Message -----
From: Serguei Mokhov <sa_mokho@alcor.concordia.ca>
To: Peter Eisentraut <peter_e@gmx.net>
Sent: Wednesday, August 01, 2001 1:50 AM
Subject: Re: [HACKERS] Translators wanted
> ----- Original Message -----
> From: Peter Eisentraut <peter_e@gmx.net>
> To: Serguei Mokhov <sa_mokho@alcor.concordia.ca>
> Cc: <pgsql-general@postgresql.org>
> Sent: Monday, July 16, 2001 4:03 PM
>
>
> > Serguei Mokhov writes:
> >
> > > Are there people working on the translation into the Russian language?
> > > If yes, then what messages are you working on and what encoding are you using?
> > > I can start translating the messages, just want to make sure so that we
> > > don't duplicate the effort.
> >
> > Use the koi8-r encoding unless you have strong reasons against it.
>
> Well, the KOI8-R is the standard encoding, no objection. However, Win32 apps
> use Windows-1251, which is pretty common on Win machines (e.g. pgAdmin tool
> on Windows will have to have messages in this exactly encoding), or console
> Windows apps by historical reasons (from DOS) use the 866 code page. If people
> write standard Windows or console client, which rely on the messages will
> get garbage most likely or will switch back to English ones.
>
> I can send the translated messages in the all mentioned encodings, but the
> problem is how will you place those files in the tree (according to the naming
> conventions ll[_RR].po one can have only one language per region per component)
> and plus, backbends probably have no way to know what kind of clients are
> connected to them and which encoding is more appropriate for the given client
> in the same language... These problems prevent different clients with the same
> language but different encoding schemes equally well display those messages to the
> user unless someone is willing (and has ideas how) to find a solution to the problems.
>
> Serguei
