Re: translator - Mailing list pgadmin-hackers

From Jean-Michel POURE
Subject Re: translator
Date
Msg-id 200307041013.47678.jm.poure@freesurf.fr
Whole thread Raw
In response to Re: translator  (Erwien Samantha Y <apache@cosinus.sederhana.or.id>)
List pgadmin-hackers
On Thursday 03 July 2003 18:31, Erwien Samantha Y wrote:
> What is the correct definition of "Cast" and "Aggregate" in PostgreSQL

In general, the translation of database object names should stick to the
English keywords. Some examples in French:

+++++++++++++++++++++++++++++++++++++++++++++++++++++++
English           -> French
+++++++++++++++++++++++++++++++++++++++++++++++++++++++
Table              -> Table
View               -> Vue (because it starts with the letter "V")
Aggregate      -> Agrégat
Cast               -> Cast (could be "transtypage", too far from English)
Index             -> Index
Foreign Key  -> Foreign Key (could be "Clé étrangère", too far from English).
Contrainst     -> Contrainte
+++++++++++++++++++++++++++++++++++++++++++++++++++++++
etc...

To decide wether a word should be translated or not, you can:
- refer to PostgreSQL on line guide at http://www.postgresql.org/idocs.
- open pgAdmin3 and try to view the SQL written in the Properties panel.

The idea is that a basic user (for example a student in class learning SQL for
the first time, not a professional with 10 years experience) should always be
able to link the translated items to the original English syntax.

If your translation is too far away from the original SQL keywords, users will
have difficulties writing their own queries ... and may switch back to
English.

You can refer to :
http://cvs.pgadmin.org/cgi-bin/viewcvs.cgi/*checkout*/pgadmin3/docs/en_US/translation_guidelines.html

CVS down at the moment...

Cheers,
Jean-Michel


pgadmin-hackers by date:

Previous
From: Jean-Michel POURE
Date:
Subject: Re: Translation management
Next
From: Jean-Michel POURE
Date:
Subject: Testing pgAdmin3 Persian RTL display