joern

Uh, I forgot to customize the css-tags on the wp-comments page. Should be fixed but needs still some finetuning.

It was necessary because of mozilla/firefox recognized the page encoding as iso-8859-1 regardless whats in the content-type meta-tag. Mozilla makes this decision because of the Apache server-headers which it normaly set to iso-8859-1.

On Windows I down’t know. On linux you could do this via ssh. As you can see I converted the hole db with no drawbacks at this time. Next problem was apache were you should have an:
AddDefaultCharset utf-8
in the configuration for your blog-directory.

If you have a linux system:
iconv -f iso-8859-15 -t utf-8 < dbdump > dbdump.1
iconv should be avialable on all glibc2 systems

Sorry, was my fault. I didn’t set $table_prefix in wp-config.php correctly. Now the upgrade went right.

The described error occured when executing the upgrade script.

I have the posts_per_rss setting to 10 but my feeds always contends posts_per_page which is 10. Your patch Mike doesnt made a diffenrence.