Обсуждение: spanish characters in postgresql
Do I need to do anything in special to view spanish characters in postgresql? In particular ASCII 164 and ASCII 165.
Francisco Reyes <lists@natserv.com> writes: > Do I need to do anything in special to view spanish characters in > postgresql? In particular ASCII 164 and ASCII 165. initdb(1) with Latin1 encoding. Regards, Manuel.
On 11 Mar 2002, Manuel Sugawara wrote: > Francisco Reyes <lists@natserv.com> writes: > > > Do I need to do anything in special to view spanish characters in > > postgresql? In particular ASCII 164 and ASCII 165. > > initdb(1) with Latin1 encoding. Thanks. A shame I will have to dropdb/createdb.. but in this case is not too bad. A new system just starting development.
Le Mardi 12 Mars 2002 00:28, Manuel Sugawara a écrit : > initdb(1) with Latin1 encoding. Do you need euro support? Latin1 does not suppor the euro symbol (and transforms it into 'euro'). It can be a problem, here, in Europe. Latin9 is recommended for euro support and replaces Latin1 (Latin9 = ISO_8859_15 = Latin1 + euro). Therefore, you should always create a database with encoding= 'Latin9'. If you really need Latin1 client side for some appplication, you can always recode characters on the fly using : SET CLIENT_ENCODING = 'Latin1'; Cheers, Jean-Michel POURE
On Tue, 2002-03-12 at 07:55, Jean-Michel POURE wrote: > Le Mardi 12 Mars 2002 00:28, Manuel Sugawara a écrit : > > initdb(1) with Latin1 encoding. > > Do you need euro support? Latin1 does not suppor the euro symbol (and > transforms it into 'euro'). It can be a problem, here, in Europe. > > Latin9 is recommended for euro support and replaces Latin1 (Latin9 = > ISO_8859_15 = Latin1 + euro). Therefore, you should always create a database > with encoding= 'Latin9'. > > If you really need Latin1 client side for some appplication, you can always > recode characters on the fly using : SET CLIENT_ENCODING = 'Latin1'; aaaaaarrrrrgggghhhhh!!!!!! Wish I had known that sooner Merci Jean-Mi Tony Grant -- RedHat Linux on Sony Vaio C1XD/S http://www.animaproductions.com/linux2.html Macromedia UltraDev with PostgreSQL http://www.animaproductions.com/ultra.html
On Tuesday, March 12, 2002, at 12:25 , Jean-Michel POURE wrote: > Le Mardi 12 Mars 2002 00:28, Manuel Sugawara a écrit : >> initdb(1) with Latin1 encoding. > > Do you need euro support? Latin1 does not suppor the euro symbol (and > transforms it into 'euro'). It can be a problem, here, in Europe. > > Latin9 is recommended for euro support and replaces Latin1 (Latin9 = > ISO_8859_15 = Latin1 + euro). Therefore, you should always > create a database > with encoding= 'Latin9'. > > If you really need Latin1 client side for some appplication, > you can always > recode characters on the fly using : SET CLIENT_ENCODING = 'Latin1'; > > Cheers, Jean-Michel POURE I'm new to databases & PostgreSQL, but wouldn't it be better to use Unicode ? And, instead of initdb, cannot one simply override the default database cluster encoding using : "CREATE DATABASE mydbname WITH ENCODING = 'unicode'" ? Also, could anyone tell me why PostgreSQL sometimes echoes it's own responses, i.e. stating things twice, like so : postgres=# SHOW CLIENT_ENCODING; NOTICE: Current client encoding is 'SQL_ASCII' NOTICE: Current client encoding is 'SQL_ASCII' SHOW VARIABLE postgres=# Cheers, Joel
Le Mercredi 13 Mars 2002 19:53, Joel Rodrigues a écrit : > I'm new to databases & PostgreSQL, but wouldn't it be better to > use Unicode ?And, instead of initdb, cannot one simply override the default > database cluster encoding using : > "CREATE DATABASE mydbname WITH ENCODING = 'unicode'" ? Yes, it is always possible. Some remarks : 1) PostgreSQL odbc driver is UTF-8 compatible but not UCS-2 compatible (UCS-2 is needed by some Microsoft products, such as Access 2K). Next version of odbc drivers will support UCS-2. 2) Some Microsoft products, such as VB, do not support Unicode at all. 3) Php can parse UTF-8 pages. But to use sub-string functions (left, right, mid), Php needs to be compiled with multi-byte options. > Also, could anyone tell me why PostgreSQL sometimes echoes it's > own responses, i.e. stating things twice, like so : > postgres=# SHOW CLIENT_ENCODING; > NOTICE: Current client encoding is 'SQL_ASCII' > NOTICE: Current client encoding is 'SQL_ASCII' > SHOW VARIABLE > postgres=# You can set SET CLIENT_ENCODING to 'Latin9' or 'Latin1' to recode data between backend and client. Please note PostgreSQL is only able to recode data from Unicode <-> Latin as for PostgreSQL 7.2+. Choose Unicode to display multiple scripts at the same time = Japanese glyphs, Arabic, etc.. and recode when needed. On the converse, it is recommended to choose a single encoding on both sides. Cheers, Jean-Michel POURE