Re: UTF8 encoding and non-text data types - Mailing list pgsql-sql

From Gregory Stark
Subject Re: UTF8 encoding and non-text data types
Date
Msg-id 87odbnidmt.fsf@oxford.xeocode.com
Whole thread Raw
In response to Re: UTF8 encoding and non-text data types  (Joe <dev@freedomcircle.net>)
Responses Re: UTF8 encoding and non-text data types
List pgsql-sql
"Joe" <dev@freedomcircle.net> writes:

> Tom Lane wrote:
>> Oh?  Interesting.  But even if we wanted to teach Postgres about that,
>> wouldn't there be a pretty strong risk of getting confused by Arabic's
>> right-to-left writing direction?  Wouldn't be real helpful if the entry
>> came out as 4321 when the user wanted 1234.  Definitely seems like
>> something that had better be left to the application side, where there's
>> more context about what the string means.
>>   
> The Arabic language is written right-to-left, except ... when it comes to
> numbers.

I don't think that matters anyways. Unicode strings are always in "logical"
order, not display order. Displaying the string in the right order is up to
the display engine in the Unicode world-view.

I'm not sure what to think about this though. It may be that Arabic notation
are close enough that it would be straightforward (IIRC decimal notation was
invented in the Arabic world after all). But other writing systems have some
pretty baroque notations which would be far more difficult to convert.

If anything I would expect this kind of conversion to live in the same place
as things like roman numerals or other more flexible formatting.

--  Gregory Stark EnterpriseDB          http://www.enterprisedb.com Ask me about EnterpriseDB's 24x7 Postgres support!


pgsql-sql by date:

Previous
From: Joe
Date:
Subject: Re: UTF8 encoding and non-text data types
Next
From: "Joost Kraaijeveld"
Date:
Subject: Is DATETIME an ANSI-SQL type?