From: | Jean-Michel POURE <jm(at)poure(dot)com> |
---|---|
To: | linas jankauskas <linas(dot)jankauskas(at)eniro(dot)lt> |
Cc: | pgadmin-hackers(at)postgresql(dot)org |
Subject: | Re: Lithuanian translation files |
Date: | 2003-12-09 09:36:04 |
Message-ID: | 200312091036.04273.jm@poure.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
Le Mardi 09 Décembre 2003 08:32, linas jankauskas a écrit :
> Please find attached two files for a lithuanian translation.
> I hope to finish this until the end of week, but you must notice, that
> not all SQL terms can be translated to lithuanian without losing of its
> meaning. F.E. all of my colleagues knows, what "View" means, but nobody
> recognizes this term, if it's translated. This is the same problem,
> which I have observed in Latvian translation progress.
Thank you very much for this partial delivery. It was published to CVS today.
Translating SQL software is always a very special case. Because users need to
be able to write the SQL queries themselves, it is recommanded to preserve
words like "View", "Triggers", etc... unless the word in your language is
quite close or widely accepted.
For example, in French, I kept "Vue" for "View". On the converse, I kept the
English word for "Trigger".
About shortcuts: the recommanded way is to keep the same shortcut letters,
otherwise drop them (unless you test them in the application, but you will
never be sure not to break something somewhere).
Regards... Jean-Michel
From | Date | Subject | |
---|---|---|---|
Next Message | Andreas Pflug | 2003-12-09 10:48:21 | Re: pgAdmin3 tl_PH translation (Partial) |
Previous Message | Jean-Michel POURE | 2003-12-09 09:27:17 | Re: pgAdmin3 tl_PH translation (Partial) |