[pgadmin-hackers] Dry Run Mode, + W9X
Hello all, What do you people think of adding a so-called dry run mode to pgAdmin? Basically, what I want is to be able to step through all the dialogs and forms and the rest of the UI in some test mode so that I can see all the GUI elements and their appearance w/o actually performing any underlying operations. This would be extremely useful for my translation work and usability testing. There some cases when I translate strings they don't fit within the allotted space in a dialog, etc, and I cannot test it/force it to appear other than in real situation. So, I'd like to have some kind of preview of the UI before I do any actual stuff (heck, I don't even always have the server available to test most common scenarios against!). For example, I'd like to be able to run through the following scenario and see all corresponding UI paths w/o actually making a connection: - Add server - Enter some dummy values - First pgAdmin pretends that the connection failed. - Then, the UI pretends the connection is successfully made and adds a fake server with fake catalog data - I can browse through the fake data. Likewise, for other functions of the UI. This would greatly help me for example not to only translate, but also test my translations where I have any Windows version (including 9X) and w/o having ability to connect to a postgres server. Since I move around quite a lot, this is a frequent scenario. Others may find it useful too. I have some ideas on implementing this. This option targets primarily the developers/translators of pgAdmin. How likely such a patch is to be accepted by the team? (Not for 1.2 of course, but for the next release). It can be some debug option... Thanks, -- Serguei A. Mokhov ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
[pgadmin-hackers] CVS Commit by andreas: Russian update
Log Message: --- Russian update Modified Files: -- pgadmin3/src/ui/ru_RU: pgadmin3.mo (r1.17 - r1.18) pgadmin3.po (r1.18 - r1.19) Index: pgadmin3.po === RCS file: /projects/pgadmin3/src/ui/ru_RU/pgadmin3.po,v retrieving revision 1.18 retrieving revision 1.19 diff -Lsrc/ui/ru_RU/pgadmin3.po -Lsrc/ui/ru_RU/pgadmin3.po -u -w -r1.18 -r1.19 --- src/ui/ru_RU/pgadmin3.po +++ src/ui/ru_RU/pgadmin3.po @@ -1,3 +1,4 @@ +# ru_RU.po # pgAdmin III Translation into Russian # # Copyright (C) Serguei Mokhov [EMAIL PROTECTED], 2003 - 2004. @@ -5,7 +6,7 @@ # $Header$ # # ChangeLog: -# - August 14 - 22, 2004: Updates for 1.2.x, Serguei Mokhov, [EMAIL PROTECTED] +# - August 14 - September 19, 2004: Updates for 1.2.x, Serguei Mokhov, [EMAIL PROTECTED] # - 2003 - 2004: Initial translation and maintenance for 1.0.x, Serguei Mokhov, [EMAIL PROTECTED] # With corrections from Vladimir Chukharev [EMAIL PROTECTED], Sun, 31 Aug 2003 00:58:02 +0300 # @@ -13,8 +14,8 @@ msgstr Project-Id-Version: pgAdmin III 1.2.x\n POT-Creation-Date: 2004-09-05 23:02+0200\n -PO-Revision-Date: 2004-09-15 11:41+0100\n -Last-Translator: \n +PO-Revision-Date: 2004-09-19 12:38-0500\n +Last-Translator: Serguei A. Mokhov [EMAIL PROTECTED]\n Language-Team: pgAdmin Developers [EMAIL PROTECTED]\n MIME-Version: 1.0\n Content-Type: text/plain; charset=utf-8\n @@ -199,7 +200,7 @@ # standard #: input:591 msgid Debug (not recommended for normal use) -msgstr Отладка (не рекомендуется для нормального использования) +msgstr Отладка (не рекоменд. для нормального использования) # standard input:16 # standard @@ -266,7 +267,7 @@ #: src/ui/frmMain.cpp:192 msgid Grant Wizard -msgstr +msgstr Мастер Выделения Прав # src/ui/frmMain.cpp:168 src/ui/frmQuery.cpp:129 standard input:16 # src/ui/frmMain.cpp:168 src/ui/frmQuery.cpp:129 standard input:32 @@ -711,12 +712,12 @@ # standard #: input:102 msgid Add the select column for ascending sort. -msgstr +msgstr Добавить выделенную колонку для сортировки по возрастанию. # standard #: input:104 msgid Add the select column for descending sort. -msgstr +msgstr Добавить выделенную колонку для сортировки по убыванию. # src/ui/dlgProperty.cpp:885 standard input:25 # src/ui/dlgProperty.cpp:885 standard input:32 @@ -799,12 +800,11 @@ #: src/ui/frmStatus.cpp:738 msgid Are you sure the logfile should be rotated? -msgstr +msgstr Вы уверены что файл журнала должен быть прокручен? #: src/ui/events.cpp:249 -#, fuzzy msgid Are you sure you wish shutdown this server? -msgstr Вы уверены, что вы хотите удалить %s %s? +msgstr Вы уверены, что вы хотите остановить этот сервер? #: src/ui/frmStatus.cpp:757 msgid Are you sure you wish to cancel the selected query(s)? @@ -816,9 +816,8 @@ msgstr Вы уверены, что вы хотите удалить %s %s? #: src/ui/events.cpp:1162 -#, fuzzy msgid Are you sure you wish to drop multiple objects? -msgstr Вы уверены, что вы хотите удалить %s %s? +msgstr Вы уверены, что вы хотите удалить многочисленные объекты? #: src/ui/frmStatus.cpp:793 msgid Are you sure you wish to terminate the selected server process(es)? @@ -1082,9 +1081,9 @@ msgstr Отменяется. #: src/ui/events.cpp:1153 -#, fuzzy, c-format +#, c-format msgid Cannot drop system %s -msgstr Нельзя удалить системный объект: %s %s. +msgstr Нельзя удалить системный объект: %s #: src/ui/events.cpp:1204 #, c-format @@ -1168,7 +1167,7 @@ #: src/ui/frmIndexcheck.cpp:49 #, c-format msgid Check Foreign Key indexes on %s %s -msgstr +msgstr Проверить индексы по вторичному ключу для %s %s # src/schema/pgObject.cpp:55 src/ui/dlgTable.cpp:438 standard input:5 # standard @@ -1226,11 +1225,11 @@ #: src/ui/frmMain.cpp:561 msgid Close database browser? If you abort, the object browser will not show accurate data. -msgstr +msgstr Закрыть браузер баз данных? Если вы отмените, браузер объектов не будет показывать аккуратную информацию. #: src/ui/frmMain.cpp:591 msgid Close server browser? If you abort, the object browser will not show accurate data. -msgstr +msgstr Закрыть браузер серверов? Если вы отмените, браузер объектов не будет показывать аккуратную информацию. msgid Close this Window. msgstr Закрыть это окно. @@ -1238,7 +1237,7 @@ # standard #: input:186 msgid Clustered -msgstr +msgstr Разбивка на страницы #: src/schema/pgIndex.cpp:209 #: src/schema/pgIndexConstraint.cpp:105 @@ -1406,7 +1405,7 @@ # standard #: input:569 msgid Confirm object deletion? -msgstr Подтвердите удаление объекта +msgstr Подтверждать удаление объекта? # standard input:8 # standard @@ -1542,7 +1541,7 @@ # standard #: src/schema/pgColumn.cpp:248 msgid Correlation -msgstr +msgstr Соотношение #: src/db/pgConn.cpp:82 #, c-format @@ -1714,7 +1713,7 @@ #: src/ui/frmMain.cpp:189 msgid Creates a backup of the current database to a local file -msgstr +msgstr
Re: [pgadmin-hackers] Translation updates for 1.2: ru_RU
Serguei Mokhov wrote: Hello Dave and Andreas, Attached are beta translations of all 1015 messages into ru_RU. The zip file contains both .po and .mo. Please install. Done. Regards, Andreas ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send unregister YourEmailAddressHere to [EMAIL PROTECTED])
Re: [pgadmin-hackers] Dry Run Mode, + W9X
Serguei Mokhov wrote: Hello all, What do you people think of adding a so-called dry run mode to pgAdmin? Basically, what I want is to be able to step through all the dialogs and forms and the rest of the UI in some test mode so that I can see all the GUI elements and their appearance w/o actually performing any underlying operations. This seems a good idea to support translators. But it has some caveats which have to be considered while implementing. E.g. a dummy server may not be written to the registry when exiting the app. Many strings which are not easily understandable without context are probably error messages. A translator would still have the problem when is this string xyz used. Win9x support is still not implementable. Our weak 9x support is not a database connection issue; it's the operating system lacking proper unicode support, which is unfortunately *the* limiting factor for your dry mode target audience. Regards, Andreas ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
Re: [pgadmin-hackers] Dry Run Mode, + W9X
- Original Message - From: Andreas Pflug [EMAIL PROTECTED] Sent: September 19, 2004 1:29 PM Serguei Mokhov wrote: Hello all, What do you people think of adding a so-called dry run mode to pgAdmin? Basically, what I want is to be able to step through all the dialogs and forms and the rest of the UI in some test mode so that I can see all the GUI elements and their appearance w/o actually performing any underlying operations. This seems a good idea to support translators. But it has some caveats which have to be considered while implementing. E.g. a dummy server may not be written to the registry when exiting the app. Yes, the point is NOT to use the registry at all in the dry run mode. It is not always I have a permission to do so where I am doing the actual work. Many strings which are not easily understandable without context are probably error messages. A translator would still have the problem when is this string xyz used. For myself, the error messages are least of my worries. Most problems I have are with field labels that cannot fit within a given container when translated, so a part of a label's text gets truncated. For the dry run mode you need little context, you just show all possible dialogs and forms for a given action. Win9x support is still not implementable. Our weak 9x support is not a database connection issue; it's the operating system lacking proper unicode support, which is unfortunately *the* limiting factor for your dry mode target audience. Nonetheless, Dave Page built 9X binaries for 1.0.2, which work perfectly okay for me. Another reason is the registry usage, but as I said, I want to avoid the use of registry in the dry run mode altogether. So, if I address the caveats and other issues that come up and if the change is not too invasive, I have some chances for the work to be applied when I contribute it? Regards, Andreas -s ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send unregister YourEmailAddressHere to [EMAIL PROTECTED])
Re: [pgadmin-hackers] Dry Run Mode, + W9X
Serguei Mokhov wrote: For myself, the error messages are least of my worries. Most problems I have are with field labels that cannot fit within a given container when translated, so a part of a label's text gets truncated. For the dry run mode you need little context, you just show all possible dialogs and forms for a given action. OK, that's reasonable. Nonetheless, Dave Page built 9X binaries for 1.0.2, which work perfectly okay for me. Another reason is the registry usage, but as I said, I want to avoid the use of registry in the dry run mode altogether. Our project doesn't contain non-unicode support any more. So, if I address the caveats and other issues that come up and if the change is not too invasive, I have some chances for the work to be applied when I contribute it? Yes, but not before 1.2 release (which will not take too much time) It will be hard work: - many comboboxes are filled from db, you might even force uncatched errors here. - some (few) strings are exchanged at runtime. First that comes to my mind is Users/Groups on the privileges tab, selectable by display users in privileges. You could scan for CTRL_STATIC in the sources. Regards, Andreas ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
[pgadmin-hackers] Necessity of wxstd.po
Hello all, I recall Jean-Michel mentioning that .po file which is more related to wxWindows than pgAdmin... As I see quite a few translators maintain those too within the project tree. My question is how necessary is it to translate this .po file (presumably it should be done by the wxWindows team, no?). Also, where does a user see those strings from wxstd.po? In file (and other common) dialogs and some such? Thanks, -- Serguei A. Mokhov ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [pgadmin-hackers] Dry Run Mode, + W9X
- Original Message - From: Andreas Pflug [EMAIL PROTECTED] Sent: September 19, 2004 2:17 PM Nonetheless, Dave Page built 9X binaries for 1.0.2, which work perfectly okay for me. Another reason is the registry usage, but as I said, I want to avoid the use of registry in the dry run mode altogether. Our project doesn't contain non-unicode support any more. Oops. I guess that passed by me unnoticed. :( So, if I address the caveats and other issues that come up and if the change is not too invasive, I have some chances for the work to be applied when I contribute it? Yes, but not before 1.2 release (which will not take too much time) Of course not as I said in my original post. And the feature freeze is taking place. It will be hard work: - many comboboxes are filled from db, you might even force uncatched errors here. - some (few) strings are exchanged at runtime. First that comes to my mind is Users/Groups on the privileges tab, selectable by display users in privileges. You could scan for CTRL_STATIC in the sources. It's okay. Life is not easy either. Thanks for the pointers! Regards, Andreas -s ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
[pgadmin-hackers] Unicode support on W9x
Hello all, I just upgraded my poEdit installation on W98SE and they now give the following warning: Due to Microsoft's draconian licensing terms for The Microsoft Layer for Unicode on Windows 95/98/ME, poEdit cannot ship with full Unicode support. You have to manually download unicows.exe from http://www.microsoft.com/downloads/details.aspx?FamilyId=73BA7BD7-ED06-4F0D-80A4-2A7EEAEE17E2displaylang=en and copy unicows.dll into the directory where poedit.exe is after poEdit installation is completed. Probably the same could be done with pgAdmin on 9x/Me? -- Serguei A. Mokhov ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
Re: [pgadmin-hackers] Unicode support on W9x
Serguei Mokhov wrote: Hello all, I just upgraded my poEdit installation on W98SE and they now give the following warning: Due to Microsoft's draconian licensing terms for The Microsoft Layer for Unicode on Windows 95/98/ME, poEdit cannot ship with full Unicode support. You have to manually download unicows.exe from http://www.microsoft.com/downloads/details.aspx?FamilyId=73BA7BD7-ED06-4F0D-80A4-2A7EEAEE17E2displaylang=en and copy unicows.dll into the directory where poedit.exe is after poEdit installation is completed. Probably the same could be done with pgAdmin on 9x/Me? We would have to link in a compatibility layer, more impacts unknown. Unicode on 9x is really a PITA, if it was easy we would have done it earlier. Besides, apparently there's no developer who could code and test it. And this licensing crap doesn't make it easier. So our advice is: if you can't avoid M$, definitely please do avoid 9x/ME. Regards, Andreas ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings
