Comments/Ratings for a Single Item

Unfortunately, the UTF conversion problems strikes me in several ways: I cannot edit any longer my own comments, and in my name i get an ugly (diamond with a question mark) displayed. This latter proble should be easily fixed by sending an appropriate header in the html; it is one line that reads: <meta http-equiv='Content-Type' content='text/html; charset=UTF-8'> This line should be close to the top of the page, after the tag. I don't know if this fixes the former problem, too. --J'org Knappen ((To the editors: You may delete this comment after reading it))

In my previous comment I wanted to exhibit some html tags verbatim. They were visible in the preview, but are now invisible (but still there, when you view the source of the page!)

In your case, your personid includes a non-ASCII character. I have asked David to do the same thing with the personids as he did with the itemids, but he hasn't done anything yet. Every page is already sending a header that identifies the page as UTF-8, but it is done on a site-wide basis with the .htaccess file, not on a file-by-file basis with meta tags. The problem is not in getting your browser to recognize pages as UTF-8. The problem is that many pages still include non-ASCII characters that are unrecognizable in UTF-8. I edited your name last night to change the question mark diamond into an umlauted o, but I didn't edit your personid, because that would just create a new personid. The personid problem is a more systematic one that needs to be handled on a database level with care and thoroughness.

The problem with exhibiting HTML tags verbatim is the one I know what it is. Whoever programmed the comment system needs to correct it in the following way: Any code that outputs some text inside of a HTML TEXTAREA must use htmlentities() or htmlspecialchars() function in order to convert the text before sending it to the client. The client will convert it back to the proper way when sending the form back to the server. This also needs to be corrected in the submission forms for member submitted game information page.

Also, there is still many more files that have not yet been converted to UTF-8, and still needs converted (however, most files are plain ASCII and do not need converted).