Comment 51 for bug 942050

Something I left out of post 47. The reason I'm doing this is that I have pretty much given up on the Pango folks fixing the
Symbol font rendering issues for characters above 0xA0 described in Bug #948245. The other reason is that SVG files really should only have Unicode characters, as most browsers will not show other characters correctly, yet there are still a lot of
programs in circulation that use Symbol or Wingdings instead of unicode for some characters.

I know there are a lot of holes in some of the translations, but the corresponding characters seem not to have been mapped
into the lower 64K unicode character space. Some of the missing ones have been assigned above that (like file folders, or clock faces, try U1F550), but that is problematic, as in my limited testing, Inkscape could not insert a character like that using the ^U mechanism, probably because it passes through a two byte integer.