Re: [pgadmin-hackers] pgAdmin web site translated into 11 languages

2003-12-01 Thread Andreas Pflug
Dave Page wrote:

We never had a standard desription before, but do have a tagline - for pga2 it was: 

pgAdmin II: PostgreSQL Tools for Windows.

Which I then shortened to:

pgAdmin III: PostgreSQL Tools

In addition, I always try to standardise the capitalisation of pgAdmin.
 

We *have* a good short description, it's in the online docs index.html. 
IMHO the text is very suitable for our main homepage.

Regards,
Andreas


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


Re: [pgadmin-hackers] pgAdmin web site translated into 11 languages

2003-12-01 Thread Dave Page
 

 -Original Message-
 From: Andreas Pflug [mailto:[EMAIL PROTECTED] 
 Sent: 01 December 2003 14:16
 To: Dave Page
 Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
 Subject: Re: [pgadmin-hackers] pgAdmin web site translated 
 into 11 languages
 
 We *have* a good short description, it's in the online docs 
 index.html. 
 IMHO the text is very suitable for our main homepage.

That old thing? I just knocked that up in a coupla minutes to get the
docs going. I'm reasonable happy with it, though perhaps we should look
at it more from the user pov rather than the developers as it currently
is.

Regards, Dave.

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


Re: [pgadmin-hackers] pgAdmin web site translated into 11 languages

2003-12-01 Thread Andreas Pflug
Dave Page wrote:

That old thing? I just knocked that up in a coupla minutes to get the
docs going. I'm reasonable happy with it, though perhaps we should look
at it more from the user pov rather than the developers as it currently
is.
Regards, Dave.

 

Currently, we have several problems about the website:

- A good short description is missing, just two sentences before Latest 
news starts.
- Change Log references CVS HEAD, while we should show the trunk's 
CHANGELOG.txt
- We should fix up pgAdmin3 naming. pgAdmin3 is just for internal use; 
for all public purposes we should stick to pgAdmin III rigorously. 
Unfortunately, this fix will break all translations.

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] pgAdmin web site translated into 11 languages

2003-12-01 Thread Jean-Michel POURE
Dear all,

Sorry, I was busy with work and web site RTL and could not answer before.

 - A good short description is missing, just two sentences before Latest
 news starts.

Feel free to submit anything. The interest of a short description is that it 
can be registered on search engines.

 - Change Log references CVS HEAD, while we should show the trunk's
 CHANGELOG.txt

Does it mean we need two changelogs: one for stable, one for snapshots?

 - We should fix up pgAdmin3 naming. pgAdmin3 is just for internal use;
 for all public purposes we should stick to pgAdmin III rigorously.
 Unfortunately, this fix will break all translations.

OK, but what happens when pgAdmin 3.1 comes along?

Cheers,
Jean-Michel


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


Re: [pgadmin-hackers] pgAdmin web site translated into 11 languages

2003-12-01 Thread Andreas Pflug
Jean-Michel POURE wrote:

Dear all,

Sorry, I was busy with work and web site RTL and could not answer before.

 

- A good short description is missing, just two sentences before Latest
news starts.
   

Feel free to submit anything. The interest of a short description is that it 
can be registered on search engines.

 

- Change Log references CVS HEAD, while we should show the trunk's
CHANGELOG.txt
   

Does it mean we need two changelogs: one for stable, one for snapshots?
 

We already have in cvs.

 

- We should fix up pgAdmin3 naming. pgAdmin3 is just for internal use;
for all public purposes we should stick to pgAdmin III rigorously.
Unfortunately, this fix will break all translations.
   

OK, but what happens when pgAdmin 3.1 comes along?
 

It's
pgAdmin III 1.0.2
pgAdmin III 1.1.0
pgAdmin III 2.0.0
...
IMHO the current architecture is so flexible that there's no pgAdmin IV 
to be expected in the next years.

Regards,
Andreas


---(end of broadcast)---
TIP 8: explain analyze is your friend


Re: [pgadmin-hackers] pgAdmin web site translated into 11 languages

2003-11-29 Thread Dave Page
 

 -Original Message-
 From: Jean-Michel POURE [mailto:[EMAIL PROTECTED] 
 Sent: 29 November 2003 21:42
 To: [EMAIL PROTECTED]
 Cc: [EMAIL PROTECTED]
 Subject: Re: [pgadmin-hackers] pgAdmin web site translated 
 into 11 languages
 
 Le Samedi 29 Novembre 2003 15:30, Andrej Surkov a écrit :
  I have registered pgAdmin web site on russian search engine and 
  realizes that there is no direct description of the 
 software on the site main page.
  I think it is not correct and short description in few sentences 
  should be published. That's just good style for respectable 
 software 
  and its presentation website. What do you think about it?
 
 Dear Andrej,
 
 You are right. It would be nice to agree on a standard 
 description of
 pgAdmin3 in a few sentences, for translation and registration 
 on web search engines. 
 
 [Technically, we could store these sentences in the META 
 information of the web site and extract them to the 
 pgadmin_wesite.pot file for translation.]
 
 A possible proposal:
 
 a href='http://www.pgadmin.org'pgAdmin/a is a free 
 software offering a complete set of administration and 
 development tools for PostgreSQL. The software offers a very 
 intuitive graphical interface running under multiple 
 platforms including MS Windows, GNU/Linux and FreeBSD. 
 pgAdmin Project is a collaborative project including hundreds 
 of volunteers.

Not sure about that. 'complete set' implies more than one program which there isn't. 
Also, 'hundreds' is a little one the high side...

Oh, and I object to GNU/Linux.

 Can we all discuss a standard text? We should be quite 
 carefull as the text could be publised on dozen of sites. I 
 will be away for the week-end.

We never had a standard desription before, but do have a tagline - for pga2 it was: 

pgAdmin II: PostgreSQL Tools for Windows.

Which I then shortened to:

pgAdmin III: PostgreSQL Tools

In addition, I always try to standardise the capitalisation of pgAdmin.

Regards, Dave.

---(end of broadcast)---
TIP 6: Have you searched our list archives?

   http://archives.postgresql.org


[pgadmin-hackers] pgAdmin web site translated into 11 languages

2003-11-27 Thread Jean-Michel POURE
Dear friends,

Just a short message to thank Andrej [EMAIL PROTECTED] for translating pgAdmin 
web site into Russian. His work can be previewed here:

http://snake.pgadmin.org/pgadmin3/index.php?locale=ru_RU

For translating pgAdmin website into your national language,
you only need to download and translate the following file:

http://www.pgadmin.org/pgadmin3/locale/pgadmin3_website.pot

If you have time, we would appreciate that you register pgAdmin web site in 
your country on search engines. Please use the address pointing at your 
language:

English : http://www.pgadmin.org

German: http://www.pgadmin.org/pgadmin3/index.php?locale=de_DE
Farsi: http://www.pgadmin.org/pgadmin3/index.php?locale=fa_IR
French: http://www.pgadmin.org/pgadmin3/index.php?locale=fr_FR
Indonesian: http://www.pgadmin.org/pgadmin3/index.php?locale=id_ID
German: http://www.pgadmin.org/pgadmin3/index.php?locale=de_DE
Japanese : http://www.pgadmin.org/pgadmin3/index.php?locale=ja_JP
Russian : http://www.pgadmin.org/pgadmin3/index.php?locale=ru_RU
Turkish : http://www.pgadmin.org/pgadmin3/index.php?locale=tr_TR
Simplified Chinese : http://www.pgadmin.org/pgadmin3/index.php?locale=zh_CN
Traditional Chinese : http://www.pgadmin.org/pgadmin3/index.php?locale=zh_TW

Having more users can help us attract more talented developers and will make 
sure that pgAdmin and PostgreSQL can live long a develop freely.

Do not hesitate to help us!

Best regards,
Jean-Michel Pouré




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