| From: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
|---|---|
| To: | "Roger Leigh" <rleigh(at)codelibre(dot)net>, "Peter Eisentraut" <peter_e(at)gmx(dot)net> |
| Cc: | "Alvaro Herrera" <alvherre(at)commandprompt(dot)com>, "Roger Leigh" <rleigh(at)debian(dot)org>, "Andrew Dunstan" <andrew(at)dunslane(dot)net>, "Robert Haas" <robertmhaas(at)gmail(dot)com>, "Selena Deckelmann" <selenamarie(at)gmail(dot)com>, <pgsql-hackers(at)postgresql(dot)org>, "Brad T(dot) Sliger" <brad(at)sliger(dot)org>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Subject: | Re: Unicode UTF-8 table formatting for psql text output |
| Date: | 2009-10-09 21:35:46 |
| Message-ID: | 4ACF6662020000250002B86A@gw.wicourts.gov |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Peter Eisentraut <peter_e(at)gmx(dot)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.
-Kevin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2009-10-09 21:52:07 | Re: one line comment style |
| Previous Message | Peter Eisentraut | 2009-10-09 21:28:25 | Re: Unicode UTF-8 table formatting for psql text output |