Re: Internationalized error messages
От | Peter Eisentraut |
---|---|
Тема | Re: Internationalized error messages |
Дата | |
Msg-id | Pine.LNX.4.30.0103122013270.1047-100000@peter.localdomain обсуждение исходный текст |
Ответ на | Re: Internationalized error messages (Karel Zak <zakkr@zf.jcu.cz>) |
Ответы |
Re: Internationalized error messages
|
Список | pgsql-hackers |
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. -- Peter Eisentraut peter_e@gmx.net http://yi.org/peter-e/
В списке pgsql-hackers по дате отправления: