Thread: pgAdmin III nearing beta phase
Hi all, As some of you know already we are now in feature freeze for the current development period for pgAdmin III. This means that we will now be concentrating on preparing pgAdmin III v1.2.0 for release. This time around is fairly important for us to get right, as pgAdmin III will be included in the binary distribution of PostgreSQL for Windows, and consequently is likely to attract large numbers of new users. Testing ======= We are not in beta yet of course, but bug reports from the latests CVS snapshots would be more than welcome at pgadmin-support@postgresql.org. pgAdmin releases have always been pretty stable and bug free - I'd like to make this the best yet! So, if you have time, please grab the latest version (which is also included in the PostgreSQL 8.0 Windows Installer betas) and give it a whirl. Translations ============ We have a huge number of translations for pgAdmin compared to other FOSS projects which is great. Now that we're in feature freeze, it's time to start updating the translations to reflect all the changes that have been made since 1.0. The translation web page gives most of the information anyone could need about translating pgAdmin. If anyone wants to start a new translation, please feel free. If anyone wants to help one of the existing translators, please contact them directly and let the list know if you come to an arrangement. Obviously we are grateful to our existing translators for the hard work last time around, and it would be great to hear from them all again this time! http://www.pgadmin.org/pgadmin3/translation.php Documentation ============= If anyone wishes to contribute but is not a programmer, then we would welcome any contributions and updates to the documentation. Not only could we use documentation on pgAdmin itself, but also the bundled PostgreSQL docs will need to be updated to 8.0 at some point. Thanks in advance to all contributors :-) Regards, Dave
Dave, ----- Original Message ----- From: "Dave Page" <dpage@vale-housing.co.uk> Sent: August 12, 2004 9:20 AM > Translations > ============ > > We have a huge number of translations for pgAdmin compared to other FOSS > projects which is great. Now that we're in feature freeze, it's time to > start updating the translations to reflect all the changes that have > been made since 1.0. The translation web page gives most of the > information anyone could need about translating pgAdmin. If anyone wants ... > http://www.pgadmin.org/pgadmin3/translation.php Now it says 1006, but when you follow the link to the .po file to download it, it still contains 765 messages only (total). It'd be much more friendly to add the missing/fuzzy translations dynamically off the source, say daily. Else it could be a bit confusing (not everyone reads the entire page to find out that they need to update from the current .pot file first). If you have time of course... -s
> -----Original Message----- > From: Serguei Mokhov [mailto:mokhov@cs.concordia.ca] > Sent: 12 August 2004 14:45 > To: Dave Page; pgadmin-hackers@postgresql.org > Subject: Re: pgAdmin III nearing beta phase > > Dave, > > ----- Original Message ----- > From: "Dave Page" <dpage@vale-housing.co.uk> > Sent: August 12, 2004 9:20 AM > > > Translations > > ============ > > > > We have a huge number of translations for pgAdmin compared to other > > FOSS projects which is great. Now that we're in feature > freeze, it's > > time to start updating the translations to reflect all the changes > > that have been made since 1.0. The translation web page > gives most of > > the information anyone could need about translating > pgAdmin. If anyone > > wants > ... > > http://www.pgadmin.org/pgadmin3/translation.php > > Now it says 1006, but when you follow the link to the .po > file to download it, it still contains 765 messages only (total). > It'd be much more friendly to add the missing/fuzzy > translations dynamically off the source, say daily. Else it > could be a bit confusing (not everyone reads the entire page > to find out that they need to update from the current .pot > file first). Ahh, that might explain why I just hacked the scripts to get the totals from the pot file (I know nothing about translations myself). Any ideas as to how I can automagically merge the updated pot file into all the po files? Regards, Dave.
----- Original Message ----- From: "Dave Page" <dpage@vale-housing.co.uk> Sent: August 12, 2004 9:36 AM > > > Translations > > > ============ > > > > > > We have a huge number of translations for pgAdmin compared to other > > > FOSS projects which is great. Now that we're in feature > > freeze, it's > > > time to start updating the translations to reflect all the changes > > > that have been made since 1.0. The translation web page > > gives most of > > > the information anyone could need about translating > > pgAdmin. If anyone > > > wants > > ... > > > http://www.pgadmin.org/pgadmin3/translation.php > > > > Now it says 1006, but when you follow the link to the .po > > file to download it, it still contains 765 messages only (total). > > It'd be much more friendly to add the missing/fuzzy > > translations dynamically off the source, say daily. Else it > > could be a bit confusing (not everyone reads the entire page > > to find out that they need to update from the current .pot > > file first). > > Ahh, that might explain why I just hacked the scripts to get the totals > from the pot file (I know nothing about translations myself). Any ideas > as to how I can automagically merge the updated pot file into all the po > files? Well, in the PostgreSQL itself we use the gettext tools, and the one to merge in the messages called, msgmerge (the other one is to check/format/etc is msgfmt). Thanks to Peter E. Postgres has this built into makefiles, so when you do 'make update-po', it does call msgmerge and updates the .po files required. Checkout the nls-global.mk file in Postres's src. So, I guess Peter runs a daily CVS checkout and builds those .po files, and parses the output of the script and transforms it into the table. I think it is automation of these steps (not all, some of them): http://developer.postgresql.org/~petere/nlsinfo/ Maybe Peter (Cc'd) can donate that script to pgAdmin? > Regards, Dave. -s
> -----Original Message----- > From: Serguei Mokhov [mailto:mokhov@cs.concordia.ca] > Sent: 12 August 2004 15:19 > To: Dave Page; pgadmin-hackers@postgresql.org > Cc: Peter Eisentraut > Subject: Re: pgAdmin III nearing beta phase > > Well, in the PostgreSQL itself we use the gettext tools, and > the one to merge in the messages called, msgmerge (the other > one is to check/format/etc is msgfmt). > Thanks to Peter E. Postgres has this built into makefiles, so > when you do 'make update-po', it does call msgmerge and > updates the .po files required. Checkout the nls-global.mk > file in Postres's src. > > So, I guess Peter runs a daily CVS checkout and builds those > .po files, and parses the output of the script and transforms > it into the table. > I think it is automation of these steps (not all, some of them): > > http://developer.postgresql.org/~petere/nlsinfo/ > > Maybe Peter (Cc'd) can donate that script to pgAdmin? Or, I could run the stringmerge script that we already appear to have :-) Thanks anyway! Regards, Dave.
Dave Page wrote: > Testing > ======= > > We are not in beta yet of course, but bug reports from the latests CVS > snapshots would be more than welcome at pgadmin-support@postgresql.org. > pgAdmin releases have always been pretty stable and bug free - I'd like > to make this the best yet! So, if you have time, please grab the latest > version (which is also included in the PostgreSQL 8.0 Windows Installer > betas) and give it a whirl. The current version per 2004-08-11 includes a restore wizard, which tries to simplify pg_restore handling. Its function has deliberately been reduced to a subset of pg_dump/pg_restore's capabilities (we might implement an 'expert level' later). This function needs intensive testing, and while we always state we don't guarantee for destroyed data it must be stressed that this tool is much more likely to destroy data than any other tools in pgadmin3 before if the parameters calculated from the user's input are not correct (which would be a bug). I've spent quite a lot of time to avoid that, but *please* test it carefully, I'm certainly blind for some of my own programming mistakes! Unfortunately, there's no doc so far how it *should* work, will do that ASAP. > > Translations > ============ > > We have a huge number of translations for pgAdmin compared to other FOSS > projects which is great. Now that we're in feature freeze, it's time to > start updating the translations to reflect all the changes that have > been made since 1.0. The translation web page gives most of the > information anyone could need about translating pgAdmin. If anyone wants > to start a new translation, please feel free. If anyone wants to help > one of the existing translators, please contact them directly and let > the list know if you come to an arrangement. Obviously we are grateful > to our existing translators for the hard work last time around, and it > would be great to hear from them all again this time! I wonder if we can have the installer localized as well. It will contain probably much much less cryptic strings, and should be easier to translate. OTOH, it's the very first program a user will get in touch with, so it's like the business card of pgsql. > http://www.pgadmin.org/pgadmin3/translation.php > > Documentation > ============= > > If anyone wishes to contribute but is not a programmer, then we would > welcome any contributions and updates to the documentation. Not only > could we use documentation on pgAdmin itself, but also the bundled > PostgreSQL docs will need to be updated to 8.0 at some point. Oh yeah... We could start with a consistent set of nice screenshots for all application dialogs (not all object property dialogs, of course). There have been changes to virtually all dialogs. Please note that the main window should display some sensible data, not just "tables(1): test". I'm afraid the text part will be mostly on my duty :-( 'though support would be highly appreciated. Regards, Andreas
Hi, Translated new strings and fixed old ones ;) Now translation is quite usable. I left some fuzzy strings that are partialy translated and contain words that can't be translated to latvian :( Hope it will be added to this realese? (Translation was sent long ago but it haven't added to any of realeses) Lafriks