From: | "Hiroshi Saito" <saito(at)inetrt(dot)skcapi(dot)co(dot)jp> |
---|---|
To: | Þórhallur Hálfdánarson <tolli(at)tol(dot)li> |
Cc: | <pgadmin-hackers(at)postgresql(dot)org> |
Subject: | Re: Translation: Languages |
Date: | 2003-07-16 02:11:49 |
Message-ID: | 021501c34b3f$9da2f070$1f324d80@w2k |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
Dear friend.
From: "Þórhallur Hálfdánarson" <tolli(at)tol(dot)li>
> Hi
>
> I thought this was discussed a few days back, but couldn't find the thread
and wanted to verify. Should language names be translated? (IMO: no)
>
> CVS snapshot since... two nights ago (?) indicates some to and some do not
translate it.
(snip)
>
> Perhaps a nota about this should be added to the translation guidelines?
The thought of me who is not a guidelines.
I didn't think that there was a problem in the beginning
in Japan from the viewpoint of one for the custom with the alphabet
indication.
And, it was there though it thought that it hardly became a problem
on the surface because the locale decision of the early value was smart.
But, UNICODE has a very good future.
pgAdmin3 will satisfy a requirement when it wants to operate it about the
one except for the language which one has.
An expression changes by the use after the choice. A user must understand
the language expression chosen at that time.
At that time, it thought whether a handled person had to understand English
of the base.
up did a translation again for the reason with ja_JP.
Regards,
Hiroshi-Saito
From | Date | Subject | |
---|---|---|---|
Next Message | Hiroshi Saito | 2003-07-16 03:19:05 | SystemObject show patch more. |
Previous Message | Þórhallur Hálfdánarson | 2003-07-16 01:09:56 | Translation: Languages |