translations

Started by Dennis Bjorklundover 21 years ago3 messages
#1Dennis Bjorklund
db@zigo.dhs.org

I've been going over the translation again and found 2 places that was
broken.

In libpq there was some files that was not scanned for translated strings
and in scan.l there was a call to gettext() missing which made error
messages into a mix of english and swedish (in my case).

Normally I just commit the swedish translations, but now I commited these
source fixes as well so we get fully translated error messages like:

dennis=# SEL;
FEL: syntaxfel vid eller n�ra "SEL" vid tecken 1
RAD 1: SEL;

instead of the previous

dennis=# SEL;
FEL: syntax error vid eller n�ra "SEL" at character 1
RAD 1: SEL;

which just looks stupid (in both english and swedish). If there are
complains I can revert it and send it to -patches.

Overall the translation seems to work fairly well. I have still not got a
total translation, but it's getting there. Maybe for 8.1.

--
/Dennis Bj�rklund

#2Alvaro Herrera
alvherre@dcc.uchile.cl
In reply to: Dennis Bjorklund (#1)
Re: translations

On Thu, Sep 09, 2004 at 09:09:31AM +0200, Dennis Bjorklund wrote:

I've been going over the translation again and found 2 places that was
broken.

In libpq there was some files that was not scanned for translated strings
and in scan.l there was a call to gettext() missing which made error
messages into a mix of english and swedish (in my case).

I see this problem too. I was about to complain. Not sure if this is
the best fix, but it certainly 'needs fixed'.

--
Alvaro Herrera (<alvherre[a]dcc.uchile.cl>)
"The ability to monopolize a planet is insignificant
next to the power of the source"

#3Dennis Bjorklund
db@zigo.dhs.org
In reply to: Alvaro Herrera (#2)
Re: translations

On Thu, 9 Sep 2004, Alvaro Herrera wrote:

In libpq there was some files that was not scanned for translated strings
and in scan.l there was a call to gettext() missing which made error
messages into a mix of english and swedish (in my case).

I see this problem too. I was about to complain. Not sure if this is
the best fix, but it certainly 'needs fixed'.

Since the parser calls yyerror() with strings we can't do the gettext call
beforehand, which only leaves it to be done inside the yyerror() function.

xgettext sees yyerror as a markup functions, so the strings generated by
the parser are all in the po file (but was not used since there was no
call to gettext).

--
/Dennis Bj�rklund