Stand-Alone Entry Forms aren’t converting high ASCII characters
Problem: You have set “Automatically Convert High ASCII Text to Entities” in your Global Weblog Preferences to “Yes”, and entries made in the Control Panel observe this, but entries made via a Stand-Alone Entry Form have missing characters or question marks instead of being converted.
Explanation: In order for the browser to properly parse high ASCII and unicode characters (including inputted text in form fields), the document must have a character encoding specified that supports those characters. If none is specified, the default charset is usually ISO-8859-1, which cannot handle high ASCII characters.
Solution: Specify a charset that supports high ASCII characters in the <head> section of the (X)HTML document:
<meta http-equiv="Content-Type" content="text/html;charset=utf-8">
