[pgadmin-hackers] Translation of pgAdmin III V1.2
Dear translators, recently we released the first Beta of pgAdmin III V1.2, which has some great enhancements over the 1.0 version; have a look at http://www.pgadmin.org/pgadmin3/beta . It will probably gain even more attendance than before, because the binary distribution of PostgreSQL 8.0 Beta for Windows already includes this version, integrated in a convenient installer. As a consequence, we can expect that most PostgreSQL users on Windows will maintain their database systems using pgAdmin III. The translatable strings have increased from former 765 to just over one thousand now, i.e. it's just a fraction of the work already done. We and probably many users throughout the world would be very grateful if you could contribute an updated translation. As usual, all you need can be found at http://pgadmin.postgresql.org/pgadmin3/translation.php . In case you won't be able to contribute a translation any more, please drop us a short note so we can mark the translation as vacant. Thanks for your help! Regards, Andreas for The pgAdmin Development Team ---(end of broadcast)--- TIP 8: explain analyze is your friend
Re: [pgadmin-hackers] Translation of pgAdmin III V1.2
Lauris Bukis wrote: Updated latvian translation. Thanks, applied. Regards, Andreas ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [pgadmin-hackers] Translation of pgAdmin III V1.2
Devrim GUNDUZ wrote: In case you won't be able to contribute a translation any more, please drop us a short note so we can mark the translation as vacant. I'll continue Turkish translation; but maybe I'll submit it when we are ready to final release -- I'm out of time nowadays. OK, take your time. We'll probably release final before pgsql release, since we're already quite stable (I believe :-) Regards, Andreas ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings
Re: [pgadmin-hackers] Translation of pgAdmin III V1.2
Serguei Mokhov wrote: Hello Andreas, I am maintaing the ru_RU one (and have no plans of stopping doing that). BTW, the translation page shows 1012 for some languages as Total and 1008 for others. So, there are 100% translated strings as 1008/1008 and 1012/1012... I guess the string merge was incomplete? The correct magic number is 1015, the strings aren't merged regularly. The website is updated now, might need a while until it's rsynced. Regards, Andreas ---(end of broadcast)--- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
Re: [pgadmin-hackers] Translation of pgAdmin III V1.2
Btw homepage have incorrect status. I know that yesterday I updated latvian po file with newest pot file and I had all 1015 translated strings but pgadmin homepage shows that there is 4 untranslated strings. I dowloaded latvian po file from homepage and there everything was ok (1015 translated strings). I still think that there is something wrong with translations.php script ;) Lafriks Andreas Pflug wrote: Lauris Bukis wrote: Updated latvian translation. Thanks, applied. Regards, Andreas ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [pgadmin-hackers] Translation of pgAdmin III V1.2
Lauris Bukis wrote: Btw homepage have incorrect status. I know that yesterday I updated latvian po file with newest pot file and I had all 1015 translated strings but pgadmin homepage shows that there is 4 untranslated strings. I dowloaded latvian po file from homepage and there everything was ok (1015 translated strings). I still think that there is something wrong with translations.php script ;) Oops, thanks for pointing this out. Actually, I messed up lv translation with stringmerge. Corrected in cvs now, web site will rsync soon. Regards, Andreas ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
Re: [pgadmin-hackers] Translation of pgAdmin III V1.2
- Original Message - From: Andreas Pflug [EMAIL PROTECTED] Sent: September 15, 2004 7:24 AM Serguei Mokhov wrote: Hello Andreas, I am maintaing the ru_RU one (and have no plans of stopping doing that). BTW, the translation page shows 1012 for some languages as Total and 1008 for others. So, there are 100% translated strings as 1008/1008 and 1012/1012... I guess the string merge was incomplete? The correct magic number is 1015, the strings aren't merged regularly. But even if they aren't merged regularly, shouldn't the entire thing be merged at once (like in a transaction) and not part-way through? Like some had 1008 as total, and others 1012... The website is updated now, might need a while until it's rsynced. Thanks! I am planning on revising that page and sending in a patch to also include web site translations, etc. when I have time... Regards, Andreas -s ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [pgadmin-hackers] Translation of pgAdmin III V1.2
Serguei Mokhov wrote: - Original Message - From: Andreas Pflug [EMAIL PROTECTED] Sent: September 15, 2004 7:24 AM Serguei Mokhov wrote: But even if they aren't merged regularly, shouldn't the entire thing be merged at once (like in a transaction) and not part-way through? Like some had 1008 as total, and others 1012... No. You can update from template any time yourself, using pgadmin3.pot. Merging the strings centrally is just for convenience (and sometimes fails) Regards, Andreas ---(end of broadcast)--- TIP 8: explain analyze is your friend
Re: [pgadmin-hackers] Translation of pgAdmin III V1.2
On Wed, 15 Sep 2004, Andreas Pflug wrote: Date: Wed, 15 Sep 2004 15:18:57 + But even if they aren't merged regularly, shouldn't the entire thing be merged at once (like in a transaction) and not part-way through? Like some had 1008 as total, and others 1012... No. You can update from template any time yourself, using pgadmin3.pot. Yup, I know. :) Same for the web site. Merging the strings centrally is just for convenience (and sometimes fails) I see. Regards, Andreas -- Serguei A. Mokhov| /~\The ASCII Computer Science Department | \ / Ribbon Campaign Concordia University | XAgainst HTML Montreal, Quebec, Canada | / \ Email! ---(end of broadcast)--- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
