From: Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-docs@postgreSQL.org
Subject: Re: Ordering of sections in chapter 22 (Localization)
Date: Sun, 20 Mar 2011 09:37:40 +0200
Message-ID: <4D85AEC4.1010703@enterprisedb.com> (raw)
In-Reply-To: <16750.1300604795@sss.pgh.pa.us>
References: <16750.1300604795@sss.pgh.pa.us>
On 20.03.2011 09:06, Tom Lane wrote:
> I'm wondering why chapter 22 discusses locales (and now collations)
> before encodings. ISTM the logical order is the reverse, because
> encodings can be explained without reference to locales, but it's very
> difficult to cover locales without touching on encodings. There are a
> lot of forward references in sections 22.1 and 22.2 as it stands.
> So I'd like to flip this around --- any objections?
I only see these two forward references:
In 22.1.1:
> If more than one character set can be used for a locale then the specifications can take the form language_territory.codeset. For example, fr_BE.UTF-8 represents the French language (fr) as spoken in Belgium (BE), with a UTF-8 character set encoding.
In 22.2.2:
> Also, a collation is tied to a character set encoding (see Section 22.3). The same collation name may exist for different encodings.
To me, it feels natural to discuss locales and collations first. They
are a higher level feature, they affect query results and there's new
syntax for collations. Encoding is just an implementation detail, you
just have to set client and server encodings correctly to match your
locale and the OS or application.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: heikki.linnakangas@enterprisedb.com, tgl@sss.pgh.pa.us
Subject: Re: Ordering of sections in chapter 22 (Localization)
In-Reply-To: <4D85AEC4.1010703@enterprisedb.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox