Re: [pgadmin-hackers] pgAdmin3 ab sofort in Deutsch!

2003-06-06 Thread Jean-Michel POURE
Le Jeudi 5 Juin 2003 13:35, Andreas Pflug a écrit :
 Where should we publicate pgadmin3.pot for all translators? Should we
 add it to CVS? (would make it more convenient for us)
 Updating pgadmin3.pot *could* be added to Makefile, instead of calling
 stringextract manually, but this would create a lot of updates to CVS.

make languages : extracts all .po entries and publishes them to CVS.

 Where should we put the resulting *.mo files? Again, for convenience, we
 could add them to CVS.

Why not create a separate cvs_root for each language (es, de, fr, etc..). 
Translators will be free to access their own translation. After each 
translator cvs commit, it is possible to analyse the log file:

First, checkout the hiddent folder CVSROOT with : cvs checkout CVSROOT
In the loginfo file, add the following entry:

de (date; cat; (sleep 2; export CVSROOT=/path/to/.../cvsroot; cd $CVSROOT/de; 
compile to .mo; publish to CVS) )  $CVSROOT/CVSROOT/commitlog 21

Each time the translator does a commit in de, translations are compiled in 
.mo files. A cron job can run make translations to generate .po files 
eveyday.

Cheers,
Jean-Michel

---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send unregister YourEmailAddressHere to [EMAIL PROTECTED])


[pgadmin-hackers] pgAdmin3 ab sofort in Deutsch!

2003-06-06 Thread Andreas Pflug
Code to call language dependent strings is successfully added to 
pgAdmin3. It will work with wx2.4, and won't need Unicode for standard 
languages (whatever ansi considers to be a standard language :-)

To create/update the pgadmin3.pot file, which acts as input to poedit, 
the script stringextract can be used. By default, it will always append, 
so over time there will be some garbage in it. This is ok, as long as 
the app is changing. For a fresh build, simply pgadmin3.pot can be deleted.

For supporting an additional language, simply create a directory using 
the canonical name under ui.

There are some questions left:

Where should we publicate pgadmin3.pot for all translators? Should we 
add it to CVS? (would make it more convenient for us)
Updating pgadmin3.pot *could* be added to Makefile, instead of calling 
stringextract manually, but this would create a lot of updates to CVS.

Where should we put the resulting *.mo files? Again, for convenience, we 
could add them to CVS.

From now on, the Win32 version will be binarily distributed as Unicode 
version.

Regards,
Andreas
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]


Re: [pgadmin-hackers] pogAdmin3 source po file

2003-06-06 Thread Jean-Michel POURE
Le Mercredi 4 Juin 2003 17:22, Andreas Pflug a écrit :
 Proposal for directories: ui/en, ui/fr, ui/de, ...

Under GNU/Linux, all translations are stored in /usr/share/locale.
There is only one .mo file per application. In order to avoid duplicate 
entries, it is recommended to have only one .po file.

cvs_root/locale/en/LC_MESSAGES/pgadmin3.po,
cvs_root/locale/fr/LC_MESSAGES/pgadmin3.po,
etc...

/usr/share/locale/en/LC_MESSAGES/pgadmin3.mo,
/usr/share/locale/fr/LC_MESSAGES/pgadmin3.mo,
etc...

make should look for the correponding .po files and compile them. During 
make install, the .mo file is moved to /usr/share/locale

Cheers,
Jean-Michel

---(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] wxrc

2003-06-06 Thread Jean-Michel POURE
Dear friends,

Could you please highlight the path to wxrc? Thanks.

Jean-Michel

---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faqs/FAQ.html


Re: [pgadmin-hackers] Error Emails

2003-06-06 Thread frank_lupo
 Hi Frank,
 
 I'm a little concerned about all the error reports we get via email
 these day from the new error dialogue. Many of them are issues that
 don't require our help.
 
 Perhaps we should remove the email button, or at least make it require a
 little more input from the user?
 
 Regards, Dave.
 
Hi Dave,

I fix error on form type tabs show in porpety 1 tabs,
I add optional parm to LogError bSendMail for enable or disable send mail (default 
enable).
   - in frmConnect button cmdConnect is disable
   - in cmdExecute button is disable

Do you think?







Bye !!
Frank Lupo (Wolf) !!

/\_ _/\
\ o o /
--ooo-ooo---

-- 
GPG Key: http://users.jc-hosting.co.uk/frank_lupo/files/publickey.txt

WebSite: http://users.jc-hosting.co.uk/frank_lupo


--
Email.it, the professional e-mail, gratis per te: http://www.email.it/f

Sponsor:
Ricordatelo: gli altri vogliono truffarti sul web, dai dialer ai programmi
spia. Manuali.net ti consegna le armi per difenderti con oltre 700 trucchi:
Clicca qui: http://adv.email.it/cgi-bin/foclick.cgi?mid=1187d=6-6

pga2fix.zip
Description: Zip compressed data

---(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


Re: [pgadmin-hackers] pga2: problem schema

2003-06-06 Thread Dave Page
OK, done.

Regards, Dave.

 -Original Message-
 From: frank_lupo [mailto:[EMAIL PROTECTED] 
 Sent: 06 June 2003 10:04
 To: Dave Page
 Cc: pgadmin-hackers
 Subject: RE: pga2: problem schema
 
 
  
  
   -Original Message-
   From: frank_lupo [mailto:[EMAIL PROTECTED]
   Sent: 06 June 2003 07:44
   To: Dave Page
   Cc: pgadmin-hackers
   Subject: RE: pga2: problem schema
   
   the selection in psql is:
   
   --
   SELECT n.nspname as Schema,
   pg_catalog.format_type(t.oid, NULL) AS Name, 
   pg_catalog.obj_description(t.oid, 'pg_type') as 
 Description FROM 
   pg_catalog.pg_type t LEFT JOIN pg_catalog.pg_namespace n 
 ON n.oid =
   t.typnamespace WHERE (t.typrelid = 0 OR (SELECT c.relkind = 
   'c' FROM pg_catalog.pg_class c WHERE c.oid = t.typrelid)) AND 
   t.typname !~ '^_'
   AND pg_catalog.pg_type_is_visible(t.oid)
   ORDER BY 1, 2;
   --
   
  
  Hmm, what about:
  
  SELECT oid, *, pg_get_userbyid(typowner) as typeowner FROM pg_type 
  WHERE typtype != 'd' AND (typtype != 'c' OR (typtype = 'c' AND 
  typrelid = 0))
  
  That includes typtype = 'c', but only if typrelid = 0 which I think 
  should solve Marc's problem.
  
  Regards, Dave.
  
 
 Ok, it's a good solution.
 
 Please chage you in cvs.
 
 
 Question mail list
 I resubscribe to pgadmin haker and pgadmin support, using 
 [EMAIL PROTECTED], 
 [EMAIL PROTECTED],
 but I send mail to mail list , not recive mail in my addres.
 
 Why?
 
 
 Thanks
 
 Bye !!
 Frank Lupo (Wolf) !!
 
/\_ _/\
\ o o /
 --ooo-ooo---
 
 -- 
 GPG Key: http://users.jc-hosting.co.uk/frank_lupo/files/publickey.txt
 
 WebSite: http://users.jc-hosting.co.uk/frank_lupo
 
 
 
 --
 Email.it, the professional e-mail, gratis per te: 
http://www.email.it/f

Sponsor:
Digitalpix stampa le tue migliori foto digitali 
su vera carta fotografica professionale.
Clicca qui: http://adv.email.it/cgi-bin/foclick.cgi?mid=1532d=6-6

---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send unregister YourEmailAddressHere to [EMAIL PROTECTED])


[pgadmin-hackers] RE: pga2: problem schema

2003-06-06 Thread frank_lupo
 
 
  -Original Message-
  From: frank_lupo [mailto:[EMAIL PROTECTED] 
  Sent: 06 June 2003 07:44
  To: Dave Page
  Cc: pgadmin-hackers
  Subject: RE: pga2: problem schema
  
  the selection in psql is:
  
  --
  SELECT n.nspname as Schema,
  pg_catalog.format_type(t.oid, NULL) AS Name,
  pg_catalog.obj_description(t.oid, 'pg_type') as 
  Description FROM pg_catalog.pg_type t
  LEFT JOIN pg_catalog.pg_namespace n ON n.oid = 
  t.typnamespace WHERE (t.typrelid = 0 OR (SELECT c.relkind = 
  'c' FROM pg_catalog.pg_class c WHERE c.oid = t.typrelid)) AND 
  t.typname !~ '^_'
  AND pg_catalog.pg_type_is_visible(t.oid)
  ORDER BY 1, 2;
  --
  
 
 Hmm, what about:
 
 SELECT oid, *, pg_get_userbyid(typowner) as typeowner FROM pg_type WHERE
 typtype != 'd' AND (typtype != 'c' OR (typtype = 'c' AND typrelid = 0))
 
 That includes typtype = 'c', but only if typrelid = 0 which I think
 should solve Marc's problem.
 
 Regards, Dave.
 

Ok, it's a good solution.

Please chage you in cvs.


Question mail list
I resubscribe to pgadmin haker and pgadmin support, using [EMAIL PROTECTED], [EMAIL 
PROTECTED],
but I send mail to mail list , not recive mail in my addres.

Why?


Thanks

Bye !!
Frank Lupo (Wolf) !!

   /\_ _/\
   \ o o /
--ooo-ooo---

-- 
GPG Key: http://users.jc-hosting.co.uk/frank_lupo/files/publickey.txt

WebSite: http://users.jc-hosting.co.uk/frank_lupo



--
Email.it, the professional e-mail, gratis per te: http://www.email.it/f

Sponsor:
Digitalpix stampa le tue migliori foto digitali 
su vera carta fotografica professionale.
Clicca qui: http://adv.email.it/cgi-bin/foclick.cgi?mid=1532d=6-6

---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster


Re: [pgadmin-hackers] pgAdmin3 ab sofort in Deutsch!

2003-06-06 Thread Jean-Michel POURE
Dear all,

Congratulations for the language support. I have to catch up some work and 
then I will translate pgAdmin3 into French.

 Where should we publicate pgadmin3.pot for all translators? Should we
 add it to CVS? (would make it more convenient for us)

Yes.

 Updating pgadmin3.pot *could* be added to Makefile, instead of calling
 stringextract manually, but this would create a lot of updates to CVS.

CVS release numbers are not increased after a commit unless the .pot file is 
really different. So I see no problem calling a make languages by cron job 
every 6 hours or so.

 Where should we put the resulting *.mo files? Again, for convenience, we
 could add them to CVS.

Yes. Although this is not very usuall, I vote for a separate CVS folder for 
each language:

cvs_root/es_ES
cvs_root/en_US
cvs_root/de_DE
...
cvs_root/pgadmin3

Each folder will have different access codes :
user : es_ES
pass : ***

This way, it will be more conveniant to give access codes to several people at 
once (project manager, translators, re-writers). The number of translation 
files can grow quickly : pgAdmin3 strings, website .po files, pgAdmin3 manual 
.po files...

Managing a large number of languages is a turnkey for pgAdmin3 success.

Cheers,
Jean-Michel



---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faqs/FAQ.html


[pgadmin-hackers] RE: pga2: problem schema

2003-06-06 Thread frank_lupo
 
 
  -Original Message-
  From: frank_lupo [mailto:[EMAIL PROTECTED] 
  Sent: 05 June 2003 11:08
  To: Dave Page
  Subject: pga2: problem schema
  
  
  I have a problem in pgschema.
  The selection type result 0.
  The problem is SQL_GET_TYPES7_3. 
  This is changed by Marc Persuy. 
  This selectin is in error.
  Please replace previous version of SQL_GET_TYPES7_3
 
 Hmm, the old version was wrong as well as it hid custom types. See below
 from Marc Persuy (which I modified slightly to exclude toast table
 types. Any idea what it should really be?
 
 Regards, Dave.
 
 --
 
 Hello,
 
 Your product is my everyday's tool, and superb.
 
 
 
 Even with the latest version of pgAdmin, I can't see the types I defined
 on postgres 7.3.
 
=0
 A 
=0

A
 
 So I tried a small change in pg Schema\basGlobal.bas, namely :
 
 
 
 Replace this sql constant :
 
 'Public Const SQL_GET_TYPES7_3 = SELECT oid, *,
 pg_get_userbyid(typowner) as typeowner FROM pg_type WHERE typtype != 'd'
 AND typtype != 'c'
 
 
 
 by this one :
 
 Public Const SQL_GET_TYPES7_3 = SELECT pg_type.oid, *,
 pg_get_userbyid(typowner) as typeowner FROM pg_type, pg_class WHERE
 pg_type.typrelid = pg_class.oid AND pg_class.relkind in ('c','s','t')
 
 
 
 I tested and it works to get the list of defined types, but I can't see
 no function like pg_get_viewdef(viewOID) which could be applied to a
 type, so displayed screen is not very explicit..
 
 
 
 Have You got an idea to get the work fully done ?
 
 
 
 Sincerely
 
 Marc Persuy
 

Hi Da
 ve,
=0

A
the selection in psql is:

--
SELECT n.nspname as Schema,
  pg_catalog.format_type(t.oid, NULL) AS Name,
  pg_catalog.obj_description(t.oid, 'pg_type') as Description
FROM pg_catalog.pg_type t
 LEFT JOIN pg_catalog.pg_namespace n ON n.oid = t.typnamespace
WHERE (t.typrelid = 0 OR (SELECT c.relkind = 'c' FROM pg_catalog.pg_class c WHERE 
c.oid = t.typrelid)) AND t.typname !~ '^_'
  AND pg_catalog.pg_type_is_visible(t.oid)
ORDER BY 1, 2;
--

Do you think?


Bye !!
Frank Lupo (Wolf) !!

/\_ _/\
\ o o /
--ooo-ooo---

-- 
GPG Key: http://users.jc-hosting.co.uk/frank_lupo/files/publickey.txt

WebSite: http://users.jc-hosting.co.uk/frank_lupo



--
Email.it, the professional e-mail, gratis per te: http://www.email.it/f

Sponsor:
Scopri la nuovissima stampante HP. Design elegante, stampa veloce e di qualità! 
Scoprila qui!
Clicca qui: http://adv.email.it/cgi-bin/foclick.cgi?mid=764d=6-6

---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster


[pgadmin-hackers] snake.pgadmin.org

2003-06-06 Thread Dave Page
... is having his harddisk replaced today - if I get sidetracked it may
not be finished until next week.

Regards, Dave.

---(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