Re: Unicode support

Ok, I've tried to follow your steps: be sure I've already installed pgadmin
II, that's obviously the best way to intercommunicate with postgresql from
Microsoft platforms.

It was surprising that I've succeeded transferring arabic unicode to
postgresql, at least it seems to have included multibyte characters. Then
I've found two problems:

1) When I try to view tables from Access XP, the arabic letters are not
correctly displayed: I can see only the multibyte to single byte 1:1
conversion. This is not that important because I don't need to see it in
Access because the database will be seen through PHP on the web.

2) The most critical problem is that I cannot convert a table with both
french letters with accents and arabic letters. Pgadmin seems to refuse
french characters. So I've erased french records (at least records with
accents) and the database has been transferred.

As far as I can see the unicode text file from Microsoft SQL Server is not
fully UTF-8 standard, but maybe I'm wrong.

On the postgresql server side there is the message:
ERROR:  Invalid UNICODE character sequence found (0xe974e9)
So E9 74 E9 is "été" ("société" field in the 5th record)

To better understand the situation I send you in attachment the unicode TXT
file that I'm trying to import and the pgadmin log.

Thx a lot!
Bye.

At 12.14 18/02/2002 +0100, you wrote:
>Le Lundi 18 Février 2002 11:13, Nhan NGO DINH a écrit :
> > Well, you said to export data from the SQL server splitted into structure
> > and data. How to do that? I really don't have so much experience with
> > Microsoft SQL Server...
> >
> > Then: I've tried to convert with iconv an UNICODE exported table but I
> > don't see the expected results.
>
>What is the encoding of your $MS SQL database? If Unicode, no recoding is
>needed.
>
>I recommand you installed pgAdmin2 (http://pgadmi.postgresql.org) and
>followed the following steps:
>
>1) Create a Unicode database.
>
>2) Use the migration wizard to import $MS SQL Schema into PostgreSQL. It will
>handle type conversion from $MS SQL Server <-> PostgreSQL.
>
>Alternatively, you may use $MS SQL Server GUI to export schema. You will need
>to adapt schema types and objects (convert money into float8, sequences,
>etc...). This can be quite difficult in a large schema.
>
>Use pgAdmin2 graphical interface to make sure all objects are imported :
>keys, sequences, etc.. The best way is to run both GUIs at the same time to
>create the missing objects manually.
>
>3) Export the data from SQL Server into a text file using $MS SQL Server GUI.
>Alternatively, you can attach files in Access2K and export them into a text
>file.
>
>Recode the text file using : recode Latin1..u8 file_name.txt (assuming
>Latin1 is the source encoding). If the $MS SQL database is already Unicode,
>no recoding is required and you can use pgAdmin2 during the entire process.
>
>4) Import the resulting data into PostgreSQL using pgAdmin2 or pgsql \Copy
>statement.
>
>Do not hesitate to write me on pgadmin-hackers@postgresql.org for more
>support.
>
>Cheers,
>Jean-MIchel POURE
>
>---------------------------(end of broadcast)---------------------------
>TIP 2: you can get off all lists at once with the unregister command
>     (send "unregister YourEmailAddressHere" to majordomo@postgresql.org)