BUG #5391: coding issues displaying server messages

Поиск
Список
Период
Сортировка
От Victor Vargas
Тема BUG #5391: coding issues displaying server messages
Дата
Msg-id 201003252054.o2PKsBVG044836@wwwmaster.postgresql.org
обсуждение исходный текст
Ответы Re: BUG #5391: coding issues displaying server messages
Список pgsql-bugs
The following bug has been logged online:

Bug reference:      5391
Logged by:          Victor Vargas
Email address:      kamusin@gmail.com
PostgreSQL version: 8.4
Operating system:   Ubuntu Lucid
Description:        coding issues displaying server messages
Details:

This report was originally filed at:
https://bugs.edge.launchpad.net/ubuntu/+source/postgresql-8.4/+bug/544114



postgresql-8.4 on Lucid has a i18n coding issues when displays server
messages.

postgresql-8.4 template is fully translated into Spanish in Launchpad:

  lucid/+

and the translations are included in the
/usr/share/locale-langpack/es/LC_MESSAGES/postgresql-8.4.mo.

Among others, the error messages about "authentication failed" are fully
translated, as you can see here:

  lucid/+

For example, the string:

  password authentication failed for user "%s"

is translated into Spanish this way:

  la autentificación password falló para el usuario «%s»

However, if I do a mistake during authentication, the server shows the error
message in this way:

  ricardo@kadath:~$ psql -U ricardo datos
  Contraseña para usuario ricardo:
  psql: FATAL: la autentificaci?n password fall? para el usuario
<<ricardo>>

Please, note:

  1. The ó char is replaced by ?.
  2. The « and » chars has been replaced by << and >>.

Another example: the string:

  database "%s" does not exist

is translated into Spanish as

  no existe la base de datos «%s»

as you can see here:

  lucid/+

However, the error message is displayed like this:

  ricardo@kadath:~$ psql -U ricardo datos
  Contraseña para usuario ricardo:
  psql: FATAL: no existe la base de datos <<datos>>

Again, the « and » chars has been replaced by << and >>.

This issue is not psql related, because I tried using pgadmin3 with the same
results.

This issue can't be reproduced using postgresql-8.3 in Karmic.

В списке pgsql-bugs по дате отправления:

Предыдущее
От: "bortdagos"
Дата:
Сообщение: BUG #5388: bortdagos
Следующее
От: Tom Lane
Дата:
Сообщение: Re: BUG #5390: pg_dump does not check/include additional schema dependencies when writing schema/search path