Re: Unicode string literals versus the world

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Martijn van Oosterhout <kleptog(at)svana(dot)org>
Cc: Marko Kreen <markokr(at)gmail(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: Unicode string literals versus the world
Date: 2009-04-15 18:50:46
Message-ID: 49E62C86.4040009@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Martijn van Oosterhout wrote:
> On Tue, Apr 14, 2009 at 08:10:54AM -0400, Andrew Dunstan wrote:
>
>> Marko Kreen wrote:
>>
>>> I still stand on my proposal, how about extending E'' strings with
>>> unicode escapes (eg. \uXXXX)? The E'' strings are already more
>>> clearly defined than '' and they are our "own", we don't need to
>>> consider random standards, but can consider our sanity.
>>>
>> I suspect there would be lots more support in the user community, where
>> \uXXXX is well understood in a number of contexts (Java and ECMAScript,
>> for example). It's also tolerably sane.
>>
>
> By the way, that's an example of how to do it wrong, there are more
> than 2^16 unicode characters, you want to be able to support the full
> 21-bit range if you're going to do it right.
>
> FWIW, I prefer the perl syntax which simply extends \x: \x{1344}, which
> makes it clear it's hex and doesn't make assumptions as to how many
> characters are used.
>

I could live with either. Wikipedia says: "The characters outside the
first plane usually have very specialized or rare use." For years we
rejected all characters beyond the first plane, and while that's fixed
now, the volume of complaints wasn't huge.

cheers

andrew

> Have a nice day,
>

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2009-04-15 18:53:11 Re: Unicode string literals versus the world
Previous Message Marko Kreen 2009-04-15 18:41:13 Re: Unicode string literals versus the world