SVN Commit by andreas: r4806 - trunk/www/pgadmin3/cnt

Author: andreas
Date: 2005-12-07 14:40:57 +0000 (Wed, 07 Dec 2005)
New Revision: 4806

Modified:
   trunk/www/pgadmin3/cnt/cnt_translation.php
   trunk/www/pgadmin3/cnt/cnt_translation_status.php
Log:
translation info update

Modified: trunk/www/pgadmin3/cnt/cnt_translation.php
===================================================================
--- trunk/www/pgadmin3/cnt/cnt_translation.php	2005-12-07 11:04:27 UTC (rev 4805)
+++ trunk/www/pgadmin3/cnt/cnt_translation.php	2005-12-07 14:40:57 UTC (rev 4806)
@@ -62,6 +62,7 @@
 
   

   

+  

   
 
     getNbLanguages());?>
   

 	
+	
+	
 	
   

+  

   
     Kbabel which can be found in recent GNU/Linux distributions.
 
     


-	

-    Use the translation debug mode of pgAdmin III (command line option -t) to review your translation in all dialogs. You won't need a database connection
-    in that mode, but all dialog resource files (*.xrc) are required, copies to the ui directory. If you compiled in debug mode, this will be the case
-    automatically.
-    


     

       Send us the English and translated names of your language: 'French' and 'Français', 'German"' and 'Deutsch', etc.. This will allow us to modify pgAdmin i18n/pgadmin3.lng file to display the language name in pgAdmin. We will also create a directory according to your locale canonical name under /usr/share/pgadmin3/ui (GNU/Linux and other Unixes) or c:\program files\pgadmi3\ui (Win32). The list of language codes can be found on Debian site. You also check the more detailed ISO 639.2 Codes for the Representation of Names of Languages.
      


@@ -155,6 +154,10 @@
 
     
Review your translation carefully. 


       You should be able to add the appropriate i18n/language_Country/pgadmin3.mo file under an existing binary installation of pgAdmin. Then, just select the language under the File -> Options menu. Review is an important step, because somes strings do not have a real context. You will only be able to correct entries by using pgAdmin yourself...
+    

+    Use the translation debug mode of pgAdmin III (command line option -t) to review your translation in all dialogs. You won't need a database connection
+    in that mode, but all dialog resource files (*.xrc) are required, copied to the ui directory. If you compiled in debug mode, this will be the case
+    automatically.
     


 
     
When the translation is finished and reviewed, send pgadmin3.po and pgadmin3.mo files to
@@ -202,7 +205,7 @@
       Menu strings also contain hard coded shortcuts (Ctrl-X) or function keys (F5). These can be identified by a preceding \t (tab). If appropriate, the modifier key name may be translated (Ctrl-), but the key combination must remain the same in any case, because the behaviour is coded in pgAdmin source.
       


 
-    	
Most forms are not designed with resizing capabilities, because this is quite hard work. The only resizing forms are the function, view and rule property windows. Therefore, you may need to shrink the translated text to the English size. In general, we tried to leave enough space for translation texts, but if you believe there are certain places we should spend more space please let us know.
+    	
Most forms are not designed with resizing capabilities, because this is quite hard work; in addition, most dialog contents isn't sizeable in a meaningful way. The only resizing forms are the function, view and rule property windows. Therefore, you may need to shrink the translated text to the English size. In general, we tried to leave enough space for translation texts, but if you believe there are certain places we should spend more space please let us know.
       


     
   

Modified: trunk/www/pgadmin3/cnt/cnt_translation_status.php
===================================================================
--- trunk/www/pgadmin3/cnt/cnt_translation_status.php	2005-12-07 11:04:27 UTC (rev 4805)
+++ trunk/www/pgadmin3/cnt/cnt_translation_status.php	2005-12-07 14:40:57 UTC (rev 4806)
@@ -19,7 +19,8 @@
   $translated->addLanguage ("ca_ES", "Catalan", "Carme Cerdà Torres", "carmect@tv3mail.com", "pgadmin3.po","i18n/ca_ES/pgadmin3.po", "pgadmin3.pot", "pgadmin3.pot");
   $outofdate->addLanguage ("cs_CZ", "Czech", "Unmaintained", "pgadmin-hackers@postgresql.org", "pgadmin3.po","i18n/cs_CZ/pgadmin3.po", "pgadmin3.pot", "pgadmin3.pot");
   $outofdate->addLanguage ("da_DK", "Danish", "Unmaintained", "pgadmin-hackers@postgresql.org", "pgadmin3.po","i18n/da_DK/pgadmin3.po", "pgadmin3.pot", "pgadmin3.pot");
-  $outofdate->addLanguage ("de_CH", "Swiss-German", "Unmaintained", "pgadmin-hackers@postgresql.org", "pgadmin3.po", "i18n/de_CH/pgadmin3.po", "pgadmin3.pot", "pgadmin3.pot");
+// was probably a joke
+//  $outofdate->addLanguage ("de_CH", "Swiss-German", "Unmaintained", "pgadmin-hackers@postgresql.org", "pgadmin3.po", "i18n/de_CH/pgadmin3.po", "pgadmin3.pot", "pgadmin3.pot");
   $translated->addLanguage ("de_DE", "German", "Andreas Pflug", "pgadmin@pse-consulting.de", "pgadmin3.po", "i18n/de_DE/pgadmin3.po", "pgadmin3.pot", "pgadmin3.pot");
   $outofdate->addLanguage ("el_GR", "Greek", "Unmaintained", "pgadmin-hackers@postgresql.org", "pgadmin3.po","i18n/el_GR/pgadmin3.po", "pgadmin3.pot", "pgadmin3.pot");
   $translated->addLanguage ("es_ES", "Spanish", "Diego A. Gil", "diego@adminsa.com", "pgadmin3.po","i18n/es_ES/pgadmin3.po", "pgadmin3.pot", "pgadmin3.pot");