From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Michael Fuhr <mike(at)fuhr(dot)org> |
Cc: | Martijn van Oosterhout <kleptog(at)svana(dot)org>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: psql display of Unicode combining characters in 8.2 |
Date: | 2006-12-11 01:12:14 |
Message-ID: | 24385.1165799534@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Michael Fuhr <mike(at)fuhr(dot)org> writes:
> On Sun, Dec 10, 2006 at 12:30:12PM -0500, Tom Lane wrote:
>> Martijn van Oosterhout <kleptog(at)svana(dot)org> writes:
>>> On Sat, Dec 09, 2006 at 10:50:05PM -0700, Michael Fuhr wrote:
>>>> Should the code distinguish between combining characters and
>>>> zero-width control characters so the former display correctly?
>>
>>> Probably, any idea how to tell the difference?
>>
>> I'm no expert, but isn't there a specific range of Unicode code points
>> defined for combining characters?
> Yes, several, with others scattered about.
What about the other way around: use the \u output convention only for
things we can specifically identify as control chars, and assume that
anything else with zero width is a combining char? Is there anything
other than 0-31 and 128-159 that should really get the \u treatment?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2006-12-11 01:16:07 | Re: 8.2 Partition lock changes and resource queuing. |
Previous Message | Mark Kirkwood | 2006-12-10 23:47:10 | 8.2 Partition lock changes and resource queuing. |