Re: Internationalized error messages - Mailing list pgsql-hackers

From Karel Zak
Subject Re: Internationalized error messages
Date
Msg-id 20010313083058.C24468@ara.zf.jcu.cz
Whole thread Raw
In response to Re: Internationalized error messages  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers
On Mon, Mar 12, 2001 at 08:15:02PM +0100, Peter Eisentraut wrote:
> Karel Zak writes:
> 
> > > >  For transaltion to other languages I not sure with gettext() stuff on
> > > > backend -- IMHO better (faster) solution will postgres system catalog
> > > > with it.
> > >
> > > elog(ERROR, "cannot open message catalog table");
> >
> >  Sure, and what:
> >
> > elog(ERROR, gettext("can't set LC_MESSAGES"));
> >
> >  We can generate our system catalog for this by simular way as gettext, it's
> > means all messages can be in sources in English too.
> 
> When there is an error condition in the backend, the last thing you want
> to do (and are allowed to do) is accessing tables.  Also keep in mind that
> we want to internationalize other parts of the system as well, such as
> pg_dump and psql.
Agree, the pg_xxxx application are good adepts for POSIX locales, all my
previous notes are about backend error/notice messages, but forget it --
after implementation we will more judicious.

-- Karel Zak  <zakkr@zf.jcu.cz>http://home.zf.jcu.cz/~zakkr/C, PostgreSQL, PHP, WWW, http://docs.linux.cz,
http://mape.jcu.cz


pgsql-hackers by date:

Previous
From: Giles Lean
Date:
Subject: Re: RE: xlog checkpoint depends on sync() ... seems uns afe
Next
From: Frank Joerdens
Date:
Subject: Re: TOAST