Date: Wed, 3 Jul 2019 09:23:30 -0400
From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Yonatan Misgan <yonamis@dtu.edu.et>
Cc: "pgsql-translators@postgresql.org" <pgsql-translators@postgresql.org>
Subject: Re: Localization
Message-ID: <20190703132330.GA7578@alvherre.pgsql>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: 
 <AM6PR10MB30325E990305911606EAFDF894FB0@AM6PR10MB3032.EURPRD10.PROD.OUTLOOK.COM>
User-Agent: Mutt/1.9.4 (2018-02-28)
Precedence: bulk

On 2019-Jul-03, Yonatan Misgan wrote:

> Translation is only one aspect of locales. Other localization aspects are system services. There are many attributes that are needed to define a country’s cultural conventions. These attributes include besides the country’s native language, the formatting of the date and time, the representation of numbers, the symbols for currency, etc. The locale represents the knowledge needed to support the country’s native attributes. So my question is how can I handled these locale aspects (date and time, collation order, currency symbol, numeric symbol, and format ) in PostgreSQL. Thank you.

There are locale options that change behavior in various places, such as
to_char and other places.  Other than that, I don't think we have a good
answer (but we do have very detailed documentation).  If you want to
make a stab at writing an answer, we're listening.  This means you'll
have to do a lot of research by yourself.

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services