Thread: repetitive string patterns in pgadmin

repetitive string patterns in pgadmin

From
Harald Armin Massa
Date:
Hello,

last night I did a big chunk of the german translation of the pgAdmin 3 strings.

There was a repetitive pattern of:

<x> dependencies
<x> dependencies report
<x> dependents
<x> dependents report
<x> properties
<x> properties report

and for some of those additionally sth. called "listen report"

as <x> was taken from a big set, it gave a lot of strings to
translate, in a boring way with carpal tunnel risks as of the
interface of poedit.

I would love if we could find a way to have those usages separated, as in

string constant 1 = <x>
string constant 2 = "dependencies"
string constant 3 = "dependencies report"
...
which would reduce the number of strings to translate dramatically.
And, even if one <x> is not translated, as <x> is usually something
within the database, the technical adapt user of pgAdmin should be
able to figure that out. (in constrast of the fuzzy translations
poedit is suggesting)

Harald

--
Harald Armin Massa     www.2ndQuadrant.de
PostgreSQL  Training, Services  and Support

2ndQuadrant Deutschland GmbH
GF: Harald Armin Massa
Amtsgericht Stuttgart, HRB 736399

Re: repetitive string patterns in pgadmin

From
Guillaume Lelarge
Date:
On Sun, 2011-08-21 at 13:48 +0200, Harald Armin Massa wrote:
> Hello,
>
> last night I did a big chunk of the german translation of the pgAdmin 3 strings.
>
> There was a repetitive pattern of:
>
> <x> dependencies
> <x> dependencies report
> <x> dependents
> <x> dependents report
> <x> properties
> <x> properties report
>
> and for some of those additionally sth. called "listen report"
>
> as <x> was taken from a big set, it gave a lot of strings to
> translate, in a boring way with carpal tunnel risks as of the
> interface of poedit.
>
> I would love if we could find a way to have those usages separated, as in
>
> string constant 1 = <x>
> string constant 2 = "dependencies"
> string constant 3 = "dependencies report"
> ...
> which would reduce the number of strings to translate dramatically.
> And, even if one <x> is not translated, as <x> is usually something
> within the database, the technical adapt user of pgAdmin should be
> able to figure that out. (in constrast of the fuzzy translations
> poedit is suggesting)
>

Actually, we went from what you are suggesting to what we have now.
Doing as you suggest makes the translation look like crap in many
languages (french for one). Now, if you can find a way to do it, without
having crappy translations, sure, that's great, I would welcome that.
But there's good chance you can't do it. Actually, even in the gettext
manual, they ask developers to do the way we have now.


--
Guillaume
  http://blog.guillaume.lelarge.info
  http://www.dalibo.com