Fixed character region parsing in FontDescription

First off, the default ASCII characters were always included.

Second, the CharacterRegion was ignored due to incorrect deserialization.
Example:
```
      <CharacterRegion>
        <Start>32</Start>
        <End>127</End>
      </CharacterRegion>
```
This was deserialized as "add characters from `3` to `1`", which added nothing.

Thanks to these two mistakes the character region was always 32-126.
I agree that the actual issue is somewhere else, so if you have time to investigate I'd appreciate a proper fix :)