title: '' Not a valid unicode character, but in the unicode character set?
body: <p>Short story: I can't get an entity like '&#131209;' to store in a MySQL database, either by using a text field in a Ruby on Rails app (with default UTF-8 encoding) or by inputting it directly with a MySQL GUI app.</p>
  
  <p>As far as I can tell, all Chinese characters and radicals can be entered into the database without problem, but not these rarely typed 'character components.' The character mentioned above is unicode U+20089 and html entity <code>&amp;#131209;</code>
  I can get it to display on the page by entering <code>&lt;html&gt;&amp;#131209;&lt;/html&gt;</code> and removing html escaping, but I would like to store it simply as the unicode character and keep the html escaping in place. There are many other Chinese 'components' (parts of full characters, generally consisting of 2 or 3 strokes) that cause the same problem.</p>
  
  <p>According to this page, the character mentioned is in the UTF-8 charset: <a href="http://www.fileformat.info/info/unicode/char/20089/charset_support.htm" rel="nofollow noreferrer">http://www.fileformat.info/info/unicode/char/20089/charset_support.htm</a></p>
  
  <p>But on the neighboring '...20089/index.htm' page, there's an alert saying it's not a valid unicode character.</p>
  
  <p>For reference, that entity can be found in Mac OS X by searching through the character palette (international menu, "Show Character Palette"), searching by radical, and looking under the '丿' radical.</p>
  
  <p>Apologies if this is too open-ended... can a character like this be stored in a UTF-8-based database? How is this character both supported and unsupported, both present in the character set and not valid?</p>