Re: BUG #5391: coding issues displaying server messages - Mailing list pgsql-bugs

On Thu, Mar 25, 2010 at 4:54 PM, Victor Vargas <kamusin@gmail.com> wrote:
>
> The following bug has been logged online:
>
> Bug reference: =A0 =A0 =A05391
> Logged by: =A0 =A0 =A0 =A0 =A0Victor Vargas
> Email address: =A0 =A0 =A0kamusin@gmail.com
> PostgreSQL version: 8.4
> Operating system: =A0 Ubuntu Lucid
> Description: =A0 =A0 =A0 =A0coding 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:
>
> =A0lucid/+
>
> 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:
>
> =A0lucid/+
>
> For example, the string:
>
> =A0password authentication failed for user "%s"
>
> is translated into Spanish this way:
>
> =A0la autentificaci=F3n password fall=F3 para el usuario =AB%s=BB
>
> However, if I do a mistake during authentication, the server shows the er=
ror
> message in this way:
>
> =A0ricardo@kadath:~$ psql -U ricardo datos
> =A0Contrase=F1a para usuario ricardo:
> =A0psql: FATAL: la autentificaci?n password fall? para el usuario
> <<ricardo>>
>
> Please, note:
>
> =A01. The =F3 char is replaced by ?.
> =A02. The =AB and =BB chars has been replaced by << and >>.
>
> Another example: the string:
>
> =A0database "%s" does not exist
>
> is translated into Spanish as
>
> =A0no existe la base de datos =AB%s=BB
>
> as you can see here:
>
> =A0lucid/+
>
> However, the error message is displayed like this:
>
> =A0ricardo@kadath:~$ psql -U ricardo datos
> =A0Contrase=F1a para usuario ricardo:
> =A0psql: FATAL: no existe la base de datos <<datos>>
>
> Again, the =AB and =BB chars has been replaced by << and >>.
>
> This issue is not psql related, because I tried using pgadmin3 with the s=
ame
> results.
>
> This issue can't be reproduced using postgresql-8.3 in Karmic.

In several places in this message where it seems like you meant to
include a URL, I only see the string "lucid/+".  But leaving that
aside, I don't think this is a PostgreSQL bug.  Indeed, you seem to
agree, because you wrote "this issue is not psql related, because I
tried using pgadmin3 with the same results".  What I suspect is
happening is that there is some other detail of your environment which
is different between your Karmic and Lucid installations which is
causing the difference.  Unfortunately, I'm not quite sure what that
could be...

...Robert