Per, Postgres supports an automatic encoding translation between backend and frontend for some encodings.
SQL command below changes the encoding of frontend. SET CLIENT_ENCODING TO 'encoding'; An automatic encoding translation between Unicode and other encodings has been supported since PostgreSQL 7.1. Because this requires huge conversion tables, it's not enabled by default. To enable this feature, run configure with the --enable-unicode-conversion option. Note that this requires the --enable-multibyte option also. Check below for more information. http://www.us.postgresql.org/users-lounge/docs/7.1/admin/multibyte.html Naoki Shima -----Original Message----- From: Per [mailto:[EMAIL PROTECTED]] Sent: Friday, October 26, 2001 12:27 AM To: [EMAIL PROTECTED] Subject: [PHP-I18N] UNICODE Hi, To enable localization of our new platform, we thought that saving all character strings as UNICODE would be a good idea. Even if the front-end (PHP) doesn't fully support UNICODE yet, we figured it's still good to have the database in that format, for the future. We have not installed mb_string (yet). We have created a UNICODE database and started experimenting with it (PostgreSQL) ./configure --enable-multibyte createdb -E UNICODE me-e My question is: do you need to convert strings to UTF-8 before adding them to the database, or is that done "automatically"? Best regards, Per Aronsson -- PHP Internationalization Mailing List (http://www.php.net/) To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED] -- PHP Internationalization Mailing List (http://www.php.net/) To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
