Re: Status report: regex replacement - Mailing list pgsql-hackers

From Tatsuo Ishii
Subject Re: Status report: regex replacement
Date
Msg-id 20030207.110313.74751276.t-ishii@sra.co.jp
Whole thread Raw
In response to Re: Status report: regex replacement  (Hannu Krosing <hannu@tm.ee>)
Responses Re: Status report: regex replacement  (Hannu Krosing <hannu@tm.ee>)
Re: Status report: regex replacement  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers
> > Right. Also we perhaps should call LATIN1 or ISO-8859-1 more precisely
> > way since ISO-8859-1 can be encoded in either 7 bit or 8 bit(we use
> > this). I don't know what it is called though.
> 
> I don't think that calling 8-bit ISO-8859-1 ISO-8859-1 can confuse
> anybody, but UCS-2 (ISO-10646-1), UTF-8 and UTF-16 are all widely used. 

I just pointed out that ISO-8859-1 is *not* an encoding, but a
character set.

> UTF-8 seems to be the most popular, but even XML standard requires all
> compliant implementations to deal with at least both UTF-8 and UTF-16.

I don't think PostgreSQL is going to natively support UTF-16.
--
Tatsuo Ishii


pgsql-hackers by date:

Previous
From: Arjen van der Meijden
Date:
Subject: Re: COUNT and Performance ...
Next
From: Tim Allen
Date:
Subject: Re: Status report: regex replacement