Peter Eisentraut <[EMAIL PROTECTED]> writes:
> It might already help if we allowed LC_CTYPE to be attached to a
> database rather than the entire cluster, and make the user match them
> up manually. The only drawback would be that indexes on global tables
> involving upper() or lower() would no
Tom Lane wrote:
> So the problem really occurs when database_encoding is set to an
> encoding that is incompatible with the one implied by the initdb-time
> LC_CTYPE ... which we have no good way to check. Ugh.
>
> I have some vague recollection that glibc offers an API extension
> that allows thi
Am Freitag, 9. Januar 2004 16:28 schrieb Dennis Björklund:
> What does database encoding has to do with error messages and the display
> character set?
When they are sent over the wire, the messages are converted from server
(=database) encoding to client encoding.
---(e
Am Freitag, 9. Januar 2004 15:51 schrieb Tom Lane:
> Hmm. So the problem would appear if LC_CTYPE is different from the
> database encoding? Could we fix it by forcing LC_CTYPE to the database
> encoding during startup?
That would resolve quite a few problems, but I don't think there's a way to
On Fri, 9 Jan 2004, Tom Lane wrote:
> > on what it thinks is the display character set, determined via
> > LC_CTYPE (of course, a useless concept for server software).
>
> Hmm. So the problem would appear if LC_CTYPE is different from the
> database encoding? Could we fix it by forcing LC_CTYPE
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> Remember that gettext will automatically recode the strings depending
> on what it thinks is the display character set, determined via
> LC_CTYPE (of course, a useless concept for server software).
Hmm. So the problem would appear if LC_CTYPE is diff
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> Am Freitag, 9. Januar 2004 15:51 schrieb Tom Lane:
>> Hmm. So the problem would appear if LC_CTYPE is different from the
>> database encoding? Could we fix it by forcing LC_CTYPE to the database
>> encoding during startup?
> That would resolve quite
Am Freitag, 9. Januar 2004 08:08 schrieb Dennis Björklund:
> The default installation in fedora does not work very well for non
> english people. For example. if I run psql and type COMMIT i get:
>
> dennis=# commit;
> WARNING: COMMIT: ingen transaktion p g
>
> while it should say
>
> dennis=# com
On Fri, 9 Jan 2004, Tom Lane wrote:
> I seem to recall some discussion to the effect that the message catalog
> files have to be in the same encoding the database is using, because
> there's no provision in the backend for converting them on-the-fly.
Still, my cvs tree seems to work. The catalogu
=?ISO-8859-1?Q?Dennis_Bj=F6rklund?= <[EMAIL PROTECTED]> writes:
> The default installation in fedora does not work very well for non
> english people.
I seem to recall some discussion to the effect that the message catalog
files have to be in the same encoding the database is using, because
there
The default installation in fedora does not work very well for non
english people. For example. if I run psql and type COMMIT i get:
dennis=# commit;
WARNING: COMMIT: ingen transaktion p g
while it should say
dennis=# commit;
WARNING: COMMIT: ingen transaktion pågår
And those spaces in the f
11 matches
Mail list logo
