COMMON: Add string encoding API with more informative error behavior

[elasota]

This updates the string encode API to return a status code indicating whether the encoding completely succeeded, or if it contains errors.

Currently, unmappable characters are just silently encoded as "?" so there is no way to determine if a Unicode code point is valid on a particular code page other than seeing if it comes out as "?" when the input character wasn't "?" which is a pretty gnarly hack.

The mTropolis engine needs this to filter out keystrokes that don't map to a valid character.

[athrxx]

I am not sure if I understand the description correctly, but it seems that you're assuming that the keyboard events from our event manager are Unicode. They're not. At least the ports based on SDL send the keyboard events encoded as ISO 8859-1. You'll then have to know the codepage used by your game and its fonts and use that for re-encoding. There is no multibyte support for the keyboard input (only the ISO 8859-1), so you can't really find out experimentally by looking for empty codepoints or error chars. In the range from 128 to 255, you'll just get wrong characters if you use the wrong codepage, no error chars.

[elasota]

edit: Nevermind, misinterpreted. So no way to get the actual Unicode code point right now either...

[sev-]

I'd like to second the statement about mTropolis engine handling, I still like the change as it provides a good feedback to the user code.