Hello,
First of all, I'd like to thank all Pligg developers. This project is great, and I believe it's on its way to becoming a major
CMS solution. Recently, I've been developing a small-scale website in Korean using the 8.2 version. I had just finished the localization process by making changes to various php files and the language file to make it UTF-8 compatible (to allow user names,
categories, word-wrap, etc in Korean) when 9.0 was released. Now that I've upgraded to the new version on my test server, I found that I have to make similar changes to the source files again. (I also noticed that some instances in the newly added code assume single byte chars) I've read some posts on the similar issues people are having, and I thought it'd be great if the dev team performed UTF-8 compatibility tests before releases. UTF-8 compatibility can make or break its foray into the international scene, as I've observed in Korea. I've put my Pligg project on the back burner because of this issue, and I'd like to know if UTF-8 compatibility can be a top priority. Thank you!
