Re: Unicode UTF-8 table formatting for psql text output
Roger Leigh <rleigh@codelibre.net>
From: Roger Leigh <rleigh@codelibre.net>
To: Kevin Grittner <Kevin.Grittner@wicourts.gov>
Cc: Peter Eisentraut <peter_e@gmx.net>, Alvaro Herrera <alvherre@commandprompt.com>, Roger Leigh <rleigh@debian.org>, Andrew Dunstan <andrew@dunslane.net>, Robert Haas <robertmhaas@gmail.com>, Selena Deckelmann <selenamarie@gmail.com>, pgsql-hackers@postgresql.org, "Brad T. Sliger" <brad@sliger.org>, Tom Lane <tgl@sss.pgh.pa.us>
Date: 2009-10-11T20:39:37Z
Lists: pgsql-hackers
Attachments
- psql-utf8-table-10.patch (text/x-diff) patch
On Fri, Oct 09, 2009 at 04:35:46PM -0500, Kevin Grittner wrote: > Peter Eisentraut <peter_e@gmx.net> wrote: > > > I think the setting ought be called linestyle unicode (instead of > > utf8), since the same setting would presumably work in case we ever > > implement UTF-16 support on the client side. > > Yeah, anytime one gets sloppy with the distinction between a character > set and a character encoding scheme, one tends to regret it, sooner or > later. Here's we're talking about which glyphs to show -- that's > based on a character set. The attached updated patch renames all user-visible uses of "utf8" to "unicode". It also updates the documentation regarding "locale" to "psql client character set encoding" so the docs now match the code exactly. Regards, Roger -- .''`. Roger Leigh : :' : Debian GNU/Linux http://people.debian.org/~rleigh/ `. `' Printing on GNU/Linux? http://gutenprint.sourceforge.net/ `- GPG Public Key: 0x25BFB848 Please GPG sign your mail.