Thread: Localisation strings

Localisation strings

From
Jean-Michel POURE
Date:
Dear all,

Here are some non-standard language entries:

1) src/ui/frmQueryBuilder.cpp:1044 src/ui/frmQueryBuilder.cpp:1046
            wxLogError(__("Double right-handed joins are not allowed.\n")
                __("You must redraw your joins so that \"") + tmptable1 +
                __("\"\ndoes not appear on the righthand side \n")
                __("more than once. \n\n")
                __("Try switching it to the lefthand side in one\n")
                __("or more relationships."));
should use %s


2) src/ui/dlgProperty.cpp:89 src/ui/dlgProperty.cpp:91
msgid ""
": Notebook not found.\n"
"Prepare to crash!"
msgstr ""

What is a notebook?

3) pgadmin3.pot file contains a deprecated string:
Count rows if estiated less than (typo)

Cheers,
Jean-Michel


Re: Localisation strings

From
"Dave Page"
Date:

> -----Original Message-----
> From: Jean-Michel POURE [mailto:jm.poure@freesurf.fr]
> Sent: 25 June 2003 16:54
> To: pgadmin-hackers@postgresql.org
> Cc: Dave Page; Andreas Pflug
> Subject: Localisation strings
>
>
> Dear all,
>
> Here are some non-standard language entries:
>
> 1) src/ui/frmQueryBuilder.cpp:1044 src/ui/frmQueryBuilder.cpp:1046
>             wxLogError(__("Double right-handed
> joins are not allowed.\n")
>                 __("You must redraw your joins
> so that \"") + tmptable1 +
>                 __("\"\ndoes not appear on the
> righthand side \n")
>                 __("more than once. \n\n")
>                 __("Try switching it to the
> lefthand side in one\n")
>                 __("or more relationships."));
> should use %s

Ahh, the QB. Please feel free to tweak these to something you are happy
with.

> 2) src/ui/dlgProperty.cpp:89 src/ui/dlgProperty.cpp:91
> msgid ""
> ": Notebook not found.\n"
> "Prepare to crash!"
> msgstr ""
>
> What is a notebook?

A tabset. Actually I like this kind of error - it's nice to stick one
really humorous one in just to give ppl a chuckle. The trick is to put
it somewhere where it will get a laugh rather than get sworn at.

> 3) pgadmin3.pot file contains a deprecated string:
> Count rows if estiated less than (typo)

I fixed that typo on Windows a few days back but forgot the pot file. Do
I need to manually edit it, or regenerate it on a unix box?

Regards, Dave.

Re: Localisation strings

From
Andreas Pflug
Date:
>
>
>>Dear all,
>>
>>Here are some non-standard language entries:
>>
>>1) src/ui/frmQueryBuilder.cpp:1044 src/ui/frmQueryBuilder.cpp:1046
>>            wxLogError(__("Double right-handed
>>joins are not allowed.\n")
>>                __("You must redraw your joins
>>so that \"") + tmptable1 +
>>                __("\"\ndoes not appear on the
>>righthand side \n")
>>                __("more than once. \n\n")
>>                __("Try switching it to the
>>lefthand side in one\n")
>>                __("or more relationships."));
>>should use %s
>>
>>
>
>Ahh, the QB. Please feel free to tweak these to something you are happy
>with.
>
I skipped recoding these because Keith had stated there was work going
on. I'm a bit unhappy that we don't know about the state of QB (while
that nasty bug seems to be under control.

>>2) src/ui/dlgProperty.cpp:89 src/ui/dlgProperty.cpp:91
>>msgid ""
>>": Notebook not found.\n"
>>"Prepare to crash!"
>>msgstr ""
>>
>>
This should really never display... can only happen if xrc is really
messed up

>>3) pgadmin3.pot file contains a deprecated string:
>>Count rows if estiated less than (typo)
>>
>>
>
>I fixed that typo on Windows a few days back but forgot the pot file. Do
>I need to manually edit it, or regenerate it on a unix box?
>

Strings come and go...
The stringextract script will append new strings, leaving old/now unused
strings still untouched. From time to time, pgadmin3.pot can be deleted
and freshly created, which would lead to poEdit telling about deprecated
strings.

Regards,
Andreas


Re: Localisation strings

From
"Adam H. Pendleton"
Date:
Andreas Pflug wrote:

> I skipped recoding these because Keith had stated there was work going
> on. I'm a bit unhappy that we don't know about the state of QB (while
> that nasty bug seems to be under control.

While I don't know what the current state of the QB is, I can say that I
fixed the initial QB segfault only to find another one right away.  I am
currently working on trying to track down why this is happening, but
it's slow going.

ahp