pg.ddx.io pgsql-docs@postgresql.org mailing list archivehelp / color / mirror / Atom feed
Ordering of sections in chapter 22 (Localization) 3+ messages / 2 participants [nested] [flat]
* Ordering of sections in chapter 22 (Localization) @ 2011-03-20 07:06 Tom Lane <tgl@sss.pgh.pa.us> 0 siblings, 1 reply; 3+ messages in thread From: Tom Lane @ 2011-03-20 07:06 UTC (permalink / raw) To: pgsql-docs 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? regards, tom lane ^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: Ordering of sections in chapter 22 (Localization) @ 2011-03-20 07:37 Heikki Linnakangas <heikki.linnakangas@enterprisedb.com> parent: Tom Lane <tgl@sss.pgh.pa.us> 0 siblings, 1 reply; 3+ messages in thread From: Heikki Linnakangas @ 2011-03-20 07:37 UTC (permalink / raw) To: Tom Lane <tgl@sss.pgh.pa.us>; +Cc: pgsql-docs 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 ^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: Ordering of sections in chapter 22 (Localization) @ 2011-03-20 17:04 Tom Lane <tgl@sss.pgh.pa.us> parent: Heikki Linnakangas <heikki.linnakangas@enterprisedb.com> 0 siblings, 0 replies; 3+ messages in thread From: Tom Lane @ 2011-03-20 17:04 UTC (permalink / raw) To: Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>; +Cc: pgsql-docs Heikki Linnakangas <heikki.linnakangas@enterprisedb.com> writes: > On 20.03.2011 09:06, Tom Lane wrote: >> I'm wondering why chapter 22 discusses locales (and now collations) >> before encodings. > To me, it feels natural to discuss locales and collations first. OK, I left that alone. I can't escape the feeling that section 22.2 could do with a complete rewrite, though --- it seems awkward and full of unnecessary jargon. In particular I think we could do without the phraseology about "collation derivations". But I've been staring at it for too long now to have a good idea what to do instead. regards, tom lane ^ permalink raw reply [nested|flat] 3+ messages in thread
end of thread, other threads:[~2011-03-20 17:04 UTC | newest] Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2011-03-20 07:06 Ordering of sections in chapter 22 (Localization) Tom Lane <tgl@sss.pgh.pa.us> 2011-03-20 07:37 ` Heikki Linnakangas <heikki.linnakangas@enterprisedb.com> 2011-03-20 17:04 ` Tom Lane <tgl@sss.pgh.pa.us>
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