missing utf-8 codepages - bug resolved?

Friday 26 September 2003 11:46:18 pm - 3 replies

3 replies

Author	Message
Kai Duebbert	Saturday 27 September 2003 1:42:31 am Postgresql runs happily without it. We're using UTF-8 with postgresql and ez publish complains, but everything works just fine. kai
christian stampf	Saturday 27 September 2003 7:05:30 am kai, did you have any problems setting up the kernel_schema or the cleandata.sql ?? did you make any modifications? i am getting an error that is shown when debug is enabled. my main language is eng-US and second language chi-CN (chinese). i am pretty desperate with my current setup as my deadline is coming up... happy for any information you can provide. - chris
Kai Duebbert	Saturday 27 September 2003 7:16:11 am Chris, Yes, the error shows up in the debug report, but the site has no problems (because no conversion has to be done anyway, I think). We're using English, Chinese, and German on our site. 1. Database of Postgresql should be a unicode database. 2. Set the right charset in the configuration files (most important: the charset for the database in site.ini.append.php). See also http://ez.no/content/view/full/27999 Off you go. All running fine. Content in English, Chinese, and German. Hope this helps. (In case you're working in Shanghai, I can come round and set it up for you. ;-) ) Kai

Author

Message

Saturday 27 September 2003 1:42:31 am

Postgresql runs happily without it. We're using UTF-8 with postgresql and ez publish complains, but everything works just fine.

kai

christian stampf

Saturday 27 September 2003 7:05:30 am

kai,

did you have any problems setting up the kernel_schema or the cleandata.sql ?? did you make any modifications?

i am getting an error that is shown when debug is enabled. my main language is eng-US and second language chi-CN (chinese).

i am pretty desperate with my current setup as my deadline is coming up... happy for any information you can provide.

- chris

Kai Duebbert

Saturday 27 September 2003 7:16:11 am

Chris,

Yes, the error shows up in the debug report, but the site has no problems (because no conversion has to be done anyway, I think). We're using English, Chinese, and German on our site.

1. Database of Postgresql should be a unicode database.
2. Set the right charset in the configuration files (most important: the charset for the database in site.ini.append.php).

See also http://ez.no/content/view/full/27999

Off you go. All running fine. Content in English, Chinese, and German.

Hope this helps. (In case you're working in Shanghai, I can come round and set it up for you. ;-) )

Kai

You must be logged in to post messages in this topic!